I am trying to use Haddock for the first time on windows for a
reasonably large project.
I must be completely clueless because I seem to generate a lot of parse
errors that have no reasonable explanation.
In some cases it seems like Haddock is white space sensitive requiring
the same
Matthew Bromberg wrote:
...
I'm not sure why an auto-documentation tool shouldn't be a bit more
forgiving vis a vis it's syntax. Maybe flag errors as warnings but
keep on going.
...
I can't help you about the haddock thing but, in my experience,
if you forgive that kind of mistakes, many
Ivan Perez-4 wrote:
Matthew Bromberg wrote:
I can't help you about the haddock thing but, in my experience,
if you forgive that kind of mistakes, many users will write
documentation with
lots of warnings and say ok, these docs ain't right but, it works for
me.
I guess this is mostly
On 06/10/06, SevenThunders [EMAIL PROTECTED] wrote:
Some of these functions are really annoying to write type declarations for.
Maybe I'll get ghci to do it for me and use cut and paste :)
Try using type synonyms to bring the beasts to order.
--
-David House, [EMAIL PROTECTED]
SevenThunders wrote:
-- | compute cos (theta / 2) assuming the branch [-pi, pi]
halfcos :: Double - Double
halfcos cs = sqrt $ (cs + 1)/2
This produces a parse error
parse error in doc string: [haddock.exe: reading EOF!
on the h of the
halfcos :: Double - Double
line
David House wrote:
On 06/10/06, SevenThunders [EMAIL PROTECTED] wrote:
Some of these functions are really annoying to write type declarations
for.
Maybe I'll get ghci to do it for me and use cut and paste :)
Try using type synonyms to bring the beasts to order.
--
-David House,
