> On Unix, but it seems not on the PC version of Hugs,
> in a literate script ^M doesn't count as a whitespace character.
> Thus, if you ship a file from DOS (ugh) to Unix,
> and it has ^M at the end of every line, the Unix version
> of Hugs gives you "comment next to program line" errors.
> This is just annoying.
I don't really see this as a Hugs problem but as a file-transfer problem.
If you used Hugs on Unix and on an IBM mainframe, you'd have to convert
EBCDIC to ASCII and back again. For PC-ascii to Unix-ascii, you can do
one of the following:
1) In ftp, use ASCII mode.
2) Using zip, specify the -a (autodetect ascii files) flag.
3) Use a translator program - there's plenty about.
My favourite conversion program is: perl -p -i -e "s/\r//" *.*
4) Tell emacs on the PC to treat your Hugs files as Unix files.
(Details in emacs FAQ)
> Also, I have a fairly repeatable way to cause an
> "INTERNAL ERROR: Error in Graph" in the Windows interface
> to Hugs 1.4 beta. It comes just after I get the message:
> "Program error {Monad_[]_>>=" (that's all I see!) on the screen.
> The program is rather large, and it
> involves correcting an error and reloading.
> If you're interested in the details, I can provide them.
If the same (or similar) problem is present in the current (January 1998)
release, we're very keen to hear details.
Alastair
