\begin{itemize}
\item
A slew of small bugs are fixed. You can find the complete list
- at @http://www.cse.ogi.edu/~simonpj/ghc-bugs.html@. One
- bug remains un-fixes, namely the crash when there's an empty
+ at:
+
+\begin{verbatim}
+http://www.cse.ogi.edu/~simonpj/ghc-bugs.html
+\end{verbatim}
+
+ One bug remains un-fixes, namely the crash when there's an empty
comment at the end of file. It's wierd!
\item
\begin{itemize}
\item
-Data constructors can now have polymophic fields, and ordinary
-functions can have polymoprhic arguments. Details on
+Data constructors can now have polymorphic fields, and ordinary
+functions can have polymorphic arguments. Details on
\begin{verbatim}
http://www.cse.ogi.edu/~simonpj/quantification.html
statistics. War stories welcome.
\item
- The Heroic Efforts of \tr{Andre\' Santos <alms@di.ufpe.br>} have
+ The Heroic Efforts of \tr{Andr\'e Santos <alms@di.ufpe.br>} have
been included, AIX/RS6000 is now a supported \tr{ghc}
platform! Bug reports concerning this port to (as always)
\tr{glasgow-haskell-bugs@dcs.gla.ac.uk}.
This part of the guide is to help people upgrading from a
previous version of GHC. Right now, it is mostly to help people
-switching from GHC~0.26 (a Haskell~1.2 compiler, mostly) to GHC~2.01
-(a Haskell~1.3 compiler).
+switching from GHC~0.29 (a Haskell~1.2 compiler, mostly) to GHC~2.04
+(a Haskell~1.4 compiler).
%ToDo: index
versions of GHC, you can use the \tr{-cpp} flag and the
\tr{__GLASGOW_HASKELL__} pre-processor variable.
-For example, in GHC~0.26, \tr{__GLASGOW_HASKELL__} will be 26; for~2.01,
-it will be 201. Thus, you can write:
+For example, in GHC~0.29, \tr{__GLASGOW_HASKELL__} will be 29; for~2.04,
+it will be 204. Thus, you can write:
\begin{verbatim}
#if __HASKELL1__ <= 2
main = appendChan stdout "Hello, world!\n" exit done -- 1.2
%* *
%************************************************************************
-GHC~0.26 supported an early DRAFT of the Haskell~1.3 monadic I/O
+GHC~0.29 supported an early DRAFT of the Haskell~1.3 monadic I/O
facilities. Inevitably, what Really Made It into 1.3 is not quite
what was in the draft.
All the system modules named \tr{LibSomething} dropped the \tr{Lib}.
So: \tr{LibSystem} is now just \tr{System}.
-In~0.26, you could mix-n-match @IO@ with @PrimIO@, simply because the
+In~0.29, you could mix-n-match @IO@ with @PrimIO@, simply because the
implementation happend to allow it. Not any more.
The \tr{IOError} type is now abstract; you cannot see it's
%* *
%************************************************************************
-GHC~2.01 is fussier than 0.26 about junk in import lists. This is a
+GHC~2.04 is fussier than 0.29 about junk in import lists. This is a
feature.
\tr{Foo..} (in export lists) must be changed to \tr{module Foo}.
The \tr{LibPosix} stuff didn't make it into 1.3 I/O, so it has become
a ``system library'' (\tr{-syslib posix}). Other than dropping the
-\tr{Lib*} prefix, everything should be the same as in 0.26.
+\tr{Lib*} prefix, everything should be the same as in 0.29.
%
-% $Header: /srv/cvs/cvs.haskell.org/fptools/ghc/docs/users_guide/Attic/intro.lit,v 1.4 1997/03/24 04:42:47 sof Exp $
+% $Header: /srv/cvs/cvs.haskell.org/fptools/ghc/docs/users_guide/Attic/intro.lit,v 1.5 1997/06/06 22:19:30 sof Exp $
%
\section[introduction-GHC]{Introduction to GHC}
On the World-Wide Web, there are several URLs of likely interest:
\begin{display}
+Haskell home page -- \tr{http://haskell.org/}
GHC home page -- \tr{http://www.dcs.gla.ac.uk/fp/software/ghc/}
Glasgow FP group page -- \tr{http://www.dcs.gla.ac.uk/fp/}
-comp.lang.functional FAQ -- \tr{http://www.cs.nott.ac.uk/Department/Staff/mpj/faq.html}
-programming language research page --
- \tr{http://www.cs.cmu.edu/afs/cs.cmu.edu/user/mleone/web/language-research.html}
+comp.lang.functional FAQ --
+ \tr{http://www.cs.nott.ac.uk/Department/Staff/mpj/faq.html}
\end{display}
We run two mailing lists about Glasgow Haskell. We encourage you to
join, as you feel is appropriate.
% pointers to it. Mentioning something in the release notes is not
% the same as documenting it.
-\section[release-2-03]{Release notes for version~2.04---6/97}
+\section[release-notes]{Release notes}
+
+\subsection[release-2-04]{Release notes for version~2.04---6/97}
\input{2-04-notes.lit}
-\section[release-2-03]{Release notes for version~2.03---4/97}
+\subsection[release-2-03]{Release notes for version~2.03---4/97}
\input{2-03-notes.lit}
-\section[release-2-02]{Release notes for version~2.02---3/97}
+\subsection[release-2-02]{Release notes for version~2.02---3/97}
+\downsection
\input{2-02-notes.lit}
+\upsection
-\section[release-2-01]{Release notes for version~2.01---7/96}
-\input{2-01-notes.lit}
+%\section[release-2-01]{Release notes for version~2.01---7/96}
+%\input{2-01-notes.lit}
%\section[release-RSN]{What we hope to do Real Soon Now}
%\downsection
%with bug fixes''; i.e., the current state-of-play on the Haskell~1.2
%compiler development.
-\section{Old release notes}
+\subsection[older-release-notes]{Old release notes}
We used to include the release notes back to the dawn of time in this
document. Made for a nice long document, but it wasn't that
At present, \tr{-O2} is nearly indistinguishable from \tr{-O}.
-At version 2.01, \tr{-O} is a dodgy proposition, no matter what.
+%At version 2.01, \tr{-O} is a dodgy proposition, no matter what.
%----------------------------------------------------------------
\item[Compile via C and crank up GCC:] Even with \tr{-O}, GHC tries to
byteToInt :: Byte -> Int -- convert a Byte to Int
\end{verbatim}
-\item[\tr{Time}:]
+\item[\tr{TimeUtil}:]
\index{Time module (HBC library)}%
Manipulate time values (a Double with seconds since 1970).
+[7/97 -- this lib has been more or less superceeded by the standard Time
+ interface]
+
\begin{verbatim}
-- year mon day hour min sec dec-sec weekday
data Time = Time Int Int Int Int Int Int Double Int
\begin{onlystandalone}
\documentstyle[11pt,literate]{article}
\begin{document}
-\title{The Glorious Glasgow Haskell Compilation System\\ Version~2.02\\ User's Guide}
+\title{The Glorious Glasgow Haskell Compilation System\\ Version~2.04\\ User's Guide}
\author{The GHC Team\\
Department of Computing Science\\
University of Glasgow\\