> I sometimes encounter quite bizarre behaviour from Hugs, both 1.3 and
> 1.4. Often what happens is this: I'm happily developing a program and
> a session has been running for somewhere between 10 mins and an hour.
> All of a sudden I get a really weird output, no "error", just really
> weird output.
Happened to me, too. More often with 1.3 than 1.4. My guess is that
hugs (the program) runs OK, but the data structures (some pointers)
are messed up, perhaps due to glitches in garbage collection. It's
definitely not reproducible. That's why I didn't venture to report
this to the hugs-bugs list. But since Graeme put the subject up here,
I just like to second that observation. What I'm usually doing to fix
this is ...
> 2) I remember how Hugs has done this to me in the past, immediately
> quit the session, immediately re-start, re-load and hey presto,
> everything's ok (talk about the typical "switch the computer off and
> on again and everything will be fine"-fix to computer problems!).
That's one reason why I'd very much like to have persistent input
history between hugs sessions: the last 100 lines entered to the
interpreter are preserved in a file, say .hugs_history, just before
exiting hugs, and this file, if present, is read into the history
buffer right after starting hugs again. This is trivial to implement
as hugs already uses the gnu readline library.
Regards,
--
Johannes Waldmann Institut fur Informatik FSU D-07740 Jena Germany
http://www5.informatik.uni-jena.de/~joe/ mailto:[EMAIL PROTECTED]
