On Wed, Aug 16, 2000 at 12:15:30PM -0500, David L. Nicol wrote:
>
>If "catch" can be defined DURING PARSING
>
>and SYNTAX ERRORS are catchable
>
>error handling can be used to define otherwise
>undefined syntax, becoming a macro language.
Please take this to the -errors sublist. Thanks...
K.
-
On Wed, Aug 16, 2000 at 12:15:30PM -0500, David L. Nicol wrote:
> If "catch" can be defined DURING PARSING
>
> and SYNTAX ERRORS are catchable
>
>
> error handling can be used to define otherwise
> undefined syntax, becoming a macro language.
And AUTOLOAD can go away too! :-)
-Scott
--
Jona
> >
> > Timeouts, shouldn't be reliant on UNIX. (Although I dont think they
should
> > be in the language eigther. A system is easily developed using threads.
> > something which I hope to develop when perl6 is ready...)
> >
>
> I don't understand this paragraph.
As it stands, if you want to hav
On Tue, 08 Aug 2000, Brad hughes wrote:
> > Why not? Throw and catch are familiar to programmers.
>
> Not all programmers.
>
Oops, correct. My mistake. Even more reason not to introduce yet
another lexicon.
--
Bryan C. Warnock
([EMAIL PROTECTED])
"Bryan C. Warnock" wrote:
> On Tue, 08 Aug 2000, Peter Bevan wrote:
[...]
> > Error handling should be supported by it's own keyword
> i.e.: >
> > trap {
> > #CODE
> > }
> > release (error) {
> > # ERROR
> > }
> >
> > (just because I didn't want to steal throw and catch)
>
> Why not? Throw
Thus it was written in the epistle of Peter Scott,
>
> I do not want a language designed by a committee, or even a
> democracy. This is art, not politics.
Preach on, brother!
Ted
--
Ted Ashton ([EMAIL PROTECTED]), Info Sys, Southern Adventist University
At 06:45 PM 8/8/00 -0400, Bryan C. Warnock wrote:
>I think that Perl survived its first through fifth births because the
>idioms it chose to implement were familiar.
>
>One could conceivably create a semantically pure language with
>no platform or OS dependencies, but then no one would use it.
>
>
On Tue, 08 Aug 2000, Peter Bevan wrote:
> However, with the birth of the new Perl, I think it is time to bury those
> ideoms in the language and
> start inventing new ones..
>
Two words: "New Coke"
I think that Perl survived its first through fifth births because the
idioms it chose to implemen
please move this thread to flow as we have the error RFC posted there.
thanx,
uri
--
Uri Guttman - [EMAIL PROTECTED] -- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page --- http://www.sysarch.c
At 10:33 AM 8/8/00 -0500, Brust, Corwin wrote:
>From: Peter Bevan [mailto:[EMAIL PROTECTED]]
>
>
> >Error handling should be supported by it's own keyword i.e.:
> >
> >trap {
> > #CODE
> >}
> >release (error) {
> > # ERROR
> >}
>
This is being hashed out on per6-language-flow right now...
--
From: Peter Bevan [mailto:[EMAIL PROTECTED]]
>Error handling should be supported by it's own keyword i.e.:
>
>trap {
> #CODE
>}
>release (error) {
> # ERROR
>}
I think this is touched on by RFC# 3 wherein I ask for user definable error
messages. With those one could presumably set an erro
11 matches
Mail list logo
