the obvious reason why not: not everyone wants to use exceptions. and
there are good reasons not to use them, just like there are good reasons to
use them. therefore if optional support can be added, fine. but mandatory
requirement to use C++ exceptions is not good. what about the people who
want to use Java, or who want to write a new language, or who use C, or
PocketC, or Basic, etc etc. let's play well together.
----- Original Message -----
From: Jason Dawes <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 23, 1999 11:29 AM
Subject: Re: PalmOS improvements (was: C++ SDK wanted!)
> At 11:03 AM 9/23/99 -0700, you wrote:
> >>You kill the app if it lets exceptions out...
> >
> >That'd be great in theory. In practice, not all compilers and languages
> >support exceptions, and I'm unsure as to whether the OS should
> >mandate/enforce one way of implementing exceptions.
> >
>
> PalmOS mandates a whole bunch of other things, why not exception handling?
> It's a mistake to say that you're not going to do something because no one
> can currently handle it. If that was logical, you wouldn't have developed
> the OS in the first place, after all, no-one was writing applications for
> it before you started.
>
>
