I've converted the literate Haskell documentation and filled in the gaps
for HUnit. I've posted the darcs repository with the changes and the
new documentation at http://richardg.name/
Please email me with any feedback and/or patches that you might have.
In a bit, I'll submit the patches for
Hi Don
I've made the appropriate requests, I think, and I'll upload once they
are processed.
Richard G.
Don Stewart wrote:
richardg:
I've converted the literate Haskell documentation and filled in the gaps
for HUnit. I've posted the darcs repository with the changes and the
new
I never thought about that. I've been using Setup.hs with
#!/usr/bin/env runhaskell and never had any problems.
I guess the only thing that would be gained by using Setup.lhs is the
ability to compile the setup program. Is that something that's commonly
done?
Richard G.
Johannes Waldmann
Hello
I did a little digging on this issue and didn't find a definitive answer.
According to the Haddock page in the wiki, Haddock is the de facto way
of documenting files [http://haskell.org/haskellwiki/Haddock].
Does this mean that literate source files should be discouraged? They
seem
Hello
I've been doing some work with mutually recursive modules (MRMs). I'm
familiar with the section in the User's Guide on how to do this and have
successfully worked with MRMs with simple dependencies. However, I have
created a set of MRMs that I can't seem to get to compile because of
A pre-processor is a great idea. Template Haskell and Cabal make it
possible to extend the language by adding all kinds of funky
pre-processing (via Cabal hooks) and compile-time calculations. It
wouldn't be too difficult to add a package-specific .ehs file type with
the desired behavior.
I foggily remember previous versions of GHC being unable to create
programs that use dynamic links to libraries. Is this the case and, if
so, is it still an issue? Static linking is not an option due to
licensing issues.
I'm interested in GHC 6.6.1 and 6.8.1 on Windows, Mac (PowerPC and
Hello
I'm trying to learn how to use Template Haskell and I'm finding that the
documentation is sparse. In particular, the constructors for Dec, Exp,
Con, etc. in Language.Haskell.TH.Syntax aren't explained.
Would documentation patches be welcomed for this library?
Thanks,
Richard
I figured out a way to work around it.
Instead of pulling all patches at once, I pulled 100 at a time.
Instead of using darcs pull -a in step 3, I used darcs pull. I held
down y until about 100 or so patches were accepted and then hit d to
stop applying patches. After doing this 6 times,
I believe that there is value in having multiple BuildBots for the same
platform. More value is provided when differences are maximized between
BuildBots but there is value in having similar BuildBots (particularly,
if the similar BuildBots are popular).
Even in the relatively monoculture
Thanks for the info; I'll set up the following:
- Gentoo Linux on the G4 PPC
- OpenBSD for AMD64 for the AMD box.
It would be nifty to have an easy-to-view list showing which platforms
are covered and which platforms are desired.
Richard
Wilson MacGyver wrote:
I'm in the processing of
Hello
I have a G4 PowerPC Mac Mini and an AMD 64 bit box that I can donate
to the cause.
What OS would be the most useful on the G4? Mac OS X? Linux? BSD?
QNX (not sure if it's supported)?
What OS would be the most useful on the AMD box? BSD? QNX? Or
something else?
Richard
Simon
12 matches
Mail list logo