Including the source code in Haddock output is a good idea. Retaining
the original indentation would be tricky (but possible, the HaRe folks
have to solve a similar problem).
Marking up the source code with hyperlinks requires applying Haskell's
static scoping rules to the source code -
On Tue, Mar 01, 2005 at 09:42:17AM -, Simon Marlow wrote:
One thing I'm going to do for the 6.4 docs is include a link to the
source code file (pointing to cvs.haskell.org) for each module.
Of course this won't work when the exported names are defined elsewhere.
But I also think it would be
* Christian Maeder [EMAIL PROTECTED]:
I used gcc_2.95.3 until I discovered the warning:
LdvProfile.c:43: #error Please use gcc 3.0+ to compile this file with
DEBUG; gcc 3.0 miscompiles it
This usually happens if you use build.mk.sample. Simply remove the
-DDEBUG from the options (unless
On Thu, Feb 10, 2005 at 01:11:48PM -, Simon Marlow wrote:
We are finally at the release candidate stage for GHC 6.4. Snapshots
with versions 6.4.20050209 and later should be considered release
candidates for 6.4.
Source and Linux binary distributions are avaiable here:
Sorry it took me so long to reply.
On Mon, Feb 07, 2005 at 11:57:58AM -, Simon Marlow wrote:
On 02 February 2005 15:51, Ian Lynagh wrote:
I bet the old GHC will work fine with the new readline.
You might be right, but I'd much rather not have to check it really does
before relaxing the
http://www.haskell.org/ghc/dist/stable/dist/ghc-6-4-20050301.msi
(md5.sig: 0f3be1a0c211194415b2cb8ee579f6e1 ; size: 46M)
the only known omission from the bits intended to be included in
the release proper is the PDF version of the user's guide.
--sigbjorn
I haven't followed this thread too closely so please excuse me if this has
already been mentioned (or even fixed).
After I installed the latest binary package (20050228) the documentation was
not correctly linked from the main documentation page. 'Hierarchical
Libraries' on the main page
Donald Bruce Stewart wrote:
bstrand:
Donald Bruce Stewart wrote:
bstrand:
Simon Marlow wrote:
Just to let you know, there are a number of open bug reports for GHC on
the x86_64 platform, which seem to indicate some kind of occasional
memory/GC problem. I'm probably not going to be able to track
Ian Lynagh wrote:
[...] Is there an equivalent of this (the no-OpenGL bit):
$(MAKE) prefix=`pwd`/debian/tmp/usr install GhcLibsWithOpenGL=NO
GhcLibsWithGLUT=NO
that still works or do I have to do it by hand?
The OpenGL/GLUT/OpenAL packages (and a few others) are enabled automatically
if the
