[m-rev.] for review: MC++ stdin/stdout initialization

[Fergus Henderson]

On 19-Oct-2002, Tyson Dowd <trd at cs.mu.OZ.AU> wrote:
> 
> Possibly because it might not work as expected.
> 
> At the time the MC++ compiler was pretty buggy and my policy was not to
> change code while it was impossible to test.  Much of the time after an
> update IO didn't work at all, so making innocent looking changes while
> trying to get it to work was impossible to test.

OK, if it's just the usual ``hysterical raisons'', that's fine.
I just wanted to make sure there wasn't some particular (and still
valid) reason that you knew about.

Currently I/O in the .NET back-end doesn't work.
I am in the process of rewriting most of it.
Currently io__write_string/3 is mostly OK, but using io__stderr_stream
and io__write_string/4 is broken, and probably likewise for other stuff
that uses streams.  This is particularly painful since the code which
catches an exception and prints it out uses io__stderr_stream, so it ends
up throwing an exception... the end result is a stack overflow, with no
information about the context or content of the original exception.

Another problem is that all the text I/O stuff outputs files in Unix
format, which is wrong.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------