Yes, that's true, because we do nothing else than tracing the exceptions. It would a better example, if we would somehow repair the error on an upper level. For example we could try to load another file. The big difference to a method error() is, that you pass back control to one of the callers in the call chain. That makes sense, because the lower levels don't know, what to do in case of an error.
For me they are valuable, because the streamline my error processing. I don't want many different ways of doing error handling. Surely, it would be much nicer, if we would be able to catch exceptions from asynchronous calls. Hint, hint, Adobe :) Maybe we see something like that in the future, because the java people at the flexcoders list are asking for it too. Cheers, Ralf. On 8/29/06, Martin Heidegger <[EMAIL PROTECTED]> wrote: > Hmm - to me a method "error(...);" would do same business... > > On the other hand: Your example is a good one ;) > > Can we say in general: Exceptions are valueable if its up problems with > generic synchron input (what kind so ever)? > > yours > Martin. > > > > 2006/8/29, Ralf Bokelberg <[EMAIL PROTECTED]>: > > Code is much more often read than written. To make reading and > > understanding the code easy, we want to express our intention as > > readable as possible. Exceptions are one possibility to clearly > > state, that some error occured. > > > > Cheers, > > Ralf. > > > > On 8/29/06, erixtekila <[EMAIL PROTECTED]> wrote: > > > > I wrote a little exception handling example. You can download it from: > > > > > www.bokelberg.de/download/ExceptionHandlingExample.zip > > > OK thanks a lot Ralph. > > > I get your point : Exceptions alongside event dispatching. > > > > > > Unit tests might also follow the same purpose. > > > > > > BTW, there is nothing that can help very much in that area. > > > A developer have to be very careful to deal with them. > > > > > > So to conclude, exceptions handling can give you fine control on your > > > code, since you are aware that you don't have to miss to catch one. > > > > > > > > > > > While writing the example i found another interesting thing about > > > > exceptions: If you read the code, they communicate very clearly, that > > > > something exceptional is happening. > > > What code are you talking about ? > > > Excuse my dumbness, Ralph. > > > ----------- > > > erixtekila > > > http://blog.v-i-a.net/ > > > > > > > > > _______________________________________________ > > > osflash mailing list > > > [email protected] > > > http://osflash.org/mailman/listinfo/osflash_osflash.org > > > > > > > > > -- > > Ralf Bokelberg <[EMAIL PROTECTED]> > > Flex & Flash Consultant based in Cologne/Germany > > > > _______________________________________________ > > osflash mailing list > > [email protected] > > http://osflash.org/mailman/listinfo/osflash_osflash.org > > > > > > > -- > ICQ: 117662935 > Skype: mastakaneda > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > > > -- Ralf Bokelberg <[EMAIL PROTECTED]> Flex & Flash Consultant based in Cologne/Germany _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
