file, or putting a wrong database request or problems with file IO) can be done with Flash anyway, especially
since usually you had anyway the problem that you needed to display in one or the other way: which means
stopping the execution is something you DON'T like since its single threaded. This means there is no
(a indication could be that not even adobe used them internal) case there is no place where exceptions
are necessary. This does not apply to all Ecma implementations because others for example support
critical tasks (like haXeneko) or use it quite often internally (Mozilla's _javascript_ implementation) and they
offer quite better support for exceptions (like exception name and stacktrace)..
yours
Martin.
2006/8/27, Martin Heidegger <[EMAIL PROTECTED]>:
The only place i was really (and often) happy of having exceptions with overloading(as2lib). I think
this could be solved with a simple output almost in same quality but the problem was a lot easier
to track if the certain testcase just stopped executing. From my point of view the Exceptions caused
more trouble (within a library) than good. Of course one point or the other I have been happy that
this or that was shown in a nice way but on the other hand in needed to check exactly this case
within a generic framework (what do you do if a anonymous call throws an exception - fuck). And
this was already the as2lib exception system which is a big improvment to the inbuilt one.
yoursMartin.
--
ICQ: 117662935
Skype: mastakaneda
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
