Torsten,
I think that the advice is a good one: relying on the label only is a
good practice. Maybe we should keep that advice in the sentence. But I
think that we can drop the mention to the "experimental" nature of the
format. It has been like that for 10 years, and is not likely to change
soon.
I suggest to use a sentence like: "The following example demonstrates
how to catch a failure exception by its label only. This is the
recommended method, for it is less dependent on implementation details."
Cheers,
raph
Torsten Anders wrote:
Concerning documentation, Seif appears to be too busy to react to my
tutorial editing proposals. What do others think about this matter?
Should we do these small changes to the documentation or not?
Thank you.
Best
Torsten
On Apr 25, 2008, at 6:25 PM, Torsten Anders wrote:
BTW: since a few years, the tutorial starts with the following:
"Warning: The material in this document is still incomplete and
subject to change from day to day."
http://www.mozart-oz.org/home/doc/tutorial/index.html
Perhaps that sentence should be removed, but a warning "The material
in this chapter is still incomplete" be put at the beginning of
chapter 12, which is indeed obviously incomplete.
On Apr 25, 2008, at 6:21 PM, Torsten Anders wrote:
Dear Seif,
thank you for your reply. Would it be OK if I change the paragraph
5.11 (which presently mentions the experimental state of the system-
exceptions) into the following?
Best
Torsten
------------
5.11 System Exceptions
The exceptions raised by the Oz system are records with one of the
labels: failure, error, and system.
* failure: indicates the attempt to perform an inconsistent
equality operation on the store of Oz.
* error: indicates a runtime error which should not occur such
as applying a nonprocedure to some argument or adding an integer to
an atom, etc.
* system: indicates a runtime condition because of the
environment of the Mozart operating system process, i.e., an
unforeseeable situation like a closed file or window; or failing to
open a connection between two Mozart processes.
NEW: The following example demonstrates how to catch a failure
exception by its label.
OLD: The exact format of Mozart system-exceptions is in an
experimental state and therefore the user is advised to rely only on
the label, as in the following example:
proc {One X} X=1 end
proc {Two X} X=2 end
try {One}={Two}
catch
failure(...) then {Show caughtFailure}
end
Here the pattern failure(...) catches any record whose label is
failure. When an exception is raised but not handled, an error
message is printed in the emulator window (standard error), and the
current thread terminates. In stand-alone applications the default
behavior is that a message is printed on standard error and the whole
application terminates. It is possible to change this behavior to
something else that is more desirable for particular applications.
On Apr 25, 2008, at 5:09 PM, seif wrote:
Yes the tutorial is quite old, and I did not work on it for long time.
It should really be updated
---- Seif
Torsten Anders schrieb:
So, should the tutorial be updated (i.e. this sentence removed) to
reflect the changed stage of affairs?
Best
Torsten
On Apr 25, 2008, at 1:47 PM, Raphael Collet wrote:
Dear Rouan,
I guess the sentence you mention is in the tutorial: "The exact
format
of Mozart system-exceptions is in an experimental state..."
(http://www.mozart-oz.org/home/doc/tutorial/node5.html)
So the *format* of exceptions (record label and fields) was
considered
experimental at the time. But not the exception mechanism
itself! In
fact the format hasn't changed since, so we can consider now
that it is
no longer experimental.
Cheers,
raph
Rouan van Dalen wrote:
Hi everyone.
I have read the docs in more detail and came across the exception
mechanism provided
by Mozart. The docs indicate that the exception handling
mechanism
is in experimental
phase and is subject to change in the future.
I would just like to confirm this, and would like to know if it
has
stabilized and won't change.
Thanks for everyone's help.
Regards.
Rouan
__________________________________________________________
Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html
___________________________________________________________________
__
____________
mozart-users mailing list mozart-
[EMAIL PROTECTED]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
____________________________________________________________________
__
___________
mozart-users mailing list mozart-
[EMAIL PROTECTED]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
Office: +44-1752-233667
Private: +44-1752-558917
http://strasheela.sourceforge.net
http://www.torsten-anders.de
_____________________________________________________________________
____________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
______________________________________________________________________
___________
mozart-users mailing list mozart-
[EMAIL PROTECTED]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
Office: +44-1752-233667
Private: +44-1752-558917
http://strasheela.sourceforge.net
http://www.torsten-anders.de
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
Office: +44-1752-586227
Private: +44-1752-558917
http://strasheela.sourceforge.net
http://www.torsten-anders.de
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
