ortal, Inc
[EMAIL PROTECTED]
-Original Message-
From: Dee Jay Randall [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 2001 10:01 AM
To: [EMAIL PROTECTED]
Subject: Re: Parse Exceptions vs. fatal errors
Not that I know what I'm talking about, but would it make
sense to have
Not that I know what I'm talking about, but would it make
sense to have the parser catch all exception ids and rethrow
the ones it doesn't understand? Then if you wrote your own
input source, you would at least benefit from the exception ids
that the parser could understand (and you wouldn't ha
PROTECTED]>
Sent: Tuesday, May 29, 2001 5:14 PM
Subject: Re: Parse Exceptions vs. fatal errors
> "Jason E. Stewart" <[EMAIL PROTECTED]> writes:
>
> > I ran into a strange problem with some code. Even though I was set
> > an error handler my code was Aborting
Its pretty obvious when you think about it. The first one is a relative
path, so it was unable to build full path to it, perhaps because you started
the program in the wrong directory but the file still might be out there.
The second one is unambigiously indicated, so its sure that it tried to ope
"Jason E. Stewart" <[EMAIL PROTECTED]> writes:
> I ran into a strange problem with some code. Even though I was set
> an error handler my code was Aborting. I discovered this was because
> it was actually generating an *exception* and not an *error*.
I've dug through the documentation and I'm no
