Hi,
I'm no expert, but I've found a solution that works for me. I use the
\begin{code}
...
\end{code}
delimiters (rather than >). Since these aren't standard Latex, I
threw together a style file that called the listings package to handle
this.
The result is a file that ghc and hugs can comp
Richard,
| for almost a year now, it has been on my list of things to do to read
| thih. for reasons too detailed to get into now, except to say that I
| still use a 486 computer (sans printer) at home, I find reading dvi, ps
| and pdf inconvenient and tend to postpone reading them whereas I ten
this is addressed to Mark, but others may be interested
in my lament against papers available only in "paper-oriented"
formats (dvi, ps, pdf).
Mark P. Jones writes:
>I use exactly the kind of techniques described here in my work. For
>example, I use literate programming for the "Typing Haskell i
I agree with Mark that literate programming is messed up in Haskell. I
think that it is even worse than he says and hence I don't use it
anymore at all.
Mark P Jones wrote:
> The literate programming conventions using leading '>'s (also known
> as "Bird tracks" or the "inverted comment conventio
Koen Claessen <[EMAIL PROTECTED]> writes:
> Take a look at the following "program snippet" (a very
> popular word at last week's ICFP :-):
>
> > bfReplace :: [b] -> Tree a -> Tree b
> > bfReplace xs = deQ . bfReplaceQ xs . singletonQ
>
> Now we just have to define bfReplaceQ.
If
Hi Koen,
I think that literate programming is a great idea, but I don't
think Haskell does it justice. I'll suggest a simple solution
to your problem at the end of this message. You can skip there
now if you want ... or else read on while I rant about this some
more and describe what seems to m
This one of the reasons why I never use literate programming. I always
forget the blank lines, and then after being puzzled by the error, I
remember it, and get completely turned off.
> C Literate comments
> [...]
> To capture some cases where one omits an ">" by mistake,
> it is an erro
>
> Huh?!? Is this a bug in Hugs? Is it confused by the `<' and
> `>' in the HTML code? No! It is just doing what the
> Haskell98 report says:
>
> C Literate comments
> [...]
> To capture some cases where one omits an ">" by mistake,
> it is an error for a program line to appear adjacen
