[m-dev.] io__make_err_msg
Fergus Henderson
fjh at cs.mu.OZ.AU
Mon Jul 6 17:47:40 AEST 1998
On 06-Jul-1998, David Glen JEFFERY <dgj at cs.mu.OZ.AU> wrote:
>
> io__make_err_msg doesn't have a Prolog implementation, which means that you
> can't use Sicstus to debug the compiler. So... does anyone know how it should
> be implemented in Prolog? I guess it could just return nothing, but there may
> be a better way using some Sicstus system call I don't know about.
By default, SICStus will throw an exception if you get an I/O error.
The thrown exception will contain some information about the exact nature
of the error.
If you disable exceptions for I/O errors, as we have done (for compatibility
with NU-Prolog), then there isn't any way of getting that information,
as far as I know.
We could change things so that we don't disable exceptions for I/O errors,
and instead catch them, and save them in some global variable (via assert/1)
but that is probably not worth the effort.
--
Fergus Henderson <fjh at cs.mu.oz.au> | "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh> | of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3 | -- the last words of T. S. Garp.
More information about the developers
mailing list