mozdev.org

gnusto    

resources:
reference:
Number (decimal) Meaning
1xx Z-machine internal errors. These are caused by bugs inside Gnusto's Z-machine itself. If you see one of these, please check whether it's already been reported, and if it hasn't, report it.
100Can't modify gosub. The program passed a subroutine call into another function, but the call was too complicated for that function to be able to figure out how to insert a handler for the return value.
101Not implemented. The story attempted to use an opcode, or a feature of an opcode, that really should exist but doesn't. You should report this as an enhancement request, if it hasn't already been reported.
170
to
199
"Impossible" errors. These happen when control reaches a place it should logically never be able to reach. Obviously, this means the logic is broken.
170 impossible-- code_for_varcode()
171 impossible-- dissemble()
172 impossible-- get_prop_len()
173 impossible-- get_next_prop()
174 impossible-- get_prop()
175 impossible-- property_search()
199Extended opcode. Opcode 190 is handled specially, and so shouldn't ever be treated as an ordinary opcode. If it is, this happens.
2xx Fatal story errors. These happen when Gnusto's Z-machine thinks it's found a fault in your story that means everything has to stop. It may be wrong; if it is, it should be reported as a bug in Gnusto.
200Unknown opcode. The story used an opcode that Gnusto doesn't know. If the opcode is defined in the Z-spec, this should be reported as an enhancement request.
201Lost in space. A special case of 200. There is no opcode zero, and zero is what you're most likely to find in odd places in memory. So opcode zero triggers this error.
202Too many memory streams. A story can write a stream of data into its own memory. The spec says that a story may only have sixteen of these at once. If you try and open seventeen of them, you get this error.
203No more memory streams. If a story attempts to stop writing a stream of data into its own memory, but there isn't one to stop, it will cause this error.
204Weird output stream number. The spec defines four kinds of output streams, and the story attempted to use a number which didn't correspond to any of them.
206Unreal property. The story asked what followed a particular property of an object, and there wasn't such a property.
207Unreal cookie thrown. The story attempted to @throw something that couldn't be @thrown-- for example, because it hadn't previously been @catched.
3xxGlue errors. These are errors in the interface between Mozilla and the Z-machine.
300JavaScript compile error ("unhappy source"). This error is caused when one of Gnusto's own source code files fails to compile.
301 File not found. You asked Gnusto to load a file which doesn't exist.
302 Invalid store. The story attempted to write something invalid to memory.
303 Unearthly window. Version 5 stories have only two windows. This error occurs when they try to use one that doesn't exist.
304 Unknown effect. When Gnusto's engine wants to stop and send some sort of signal to its environment, it uses a numeric code called an "effect". This error occurs when the effect number is unknown.
307 General exception. Something happened within Gnusto which caused an exception that wasn't otherwise caught. The last-ditch handler saw it, though, and generated this error.
309 Unknown file format. You asked Gnusto to load a file, but it's not in any format it knows how to handle.
310 Prehistoric lizard. Your version of Mozilla is so old we can't reliably continue. Please upgrade.
7xx Transient story errors. These happen when Gnusto's Z-machine thinks it's found a fault in your story which can probably be worked around. It may be wrong in thinking that it's found a bug; if it is, the problem should be reported as a bug in Gnusto. Transient errors will be reported, but Gnusto will attempt to work around them.
700Spurious restore_undo. The story attempted to restore_undo without first successfully save_undoing.
701Division by zero. Gnusto will supply zero as the answer if asked to carry on.
702Illegal ZSCII code. The story attempted to output a ZSCII character outside the permitted range, which is 0-1023. Gnusto will supply 42 ('*') as the answer if asked to carry on.
703Unknown ZSCII code. The story attempted to output a ZSCII character which Gnusto didn't know how to handle. Gnusto will supply 42 ('*') as the answer if asked to carry on.
704Put undefined property. The story attempted to set a property, but didn't tell Gnusto which one. You think we're mindreaders here?
705Property too long to put. The put_prop opcode only works for properties with lengths less than three bytes.
706Property too long to get. The get_prop opcode only works for properties with lengths already less than three bytes. (You can get at the data in other ways, just not with this opcode.) Gnusto will return the first two bytes if asked to carry on.

This error is ignored by default to work around a bug in old versions of the Inform library. See bug 3314.

The gnusto project can be contacted through the mailing list or the member list.
Copyright © 2000-2017. All rights reserved. Terms of Use & Privacy Policy.