Re: Warnings, strict, and CPAN (Re: Closures and default lexical-scope for subs)

2001-02-21 Thread schwern
On Wed, Feb 21, 2001 at 05:32:50PM -0500, Sam Tregar wrote: > Examples? I know you're not talking about C or C++. I'm pretty sure > you're not talking about Java - exception-handling renders the term "fatal > error" almost meaningless. Well, an unhandled exception in Java is death for the progr

Re: Warnings, strict, and CPAN (Re: Closures and default lexical-scope for subs)

2001-02-21 Thread schwern
Its true alot languages would consider many of Perl's warnings to be errors, that's not really analgous to what we're talking about here. Run-time errors aren't quite in the same spirit as run-time warnings. A run-time error is something the language defines as being explicitly bad or a mistake (

Re: Things have paused... really?

2001-02-21 Thread schwern
On Tue, Feb 20, 2001 at 12:10:53PM -0600, Garrett Goebel wrote: > This is perhaps the 3rd recent "waiting for Larry" comment posted in the > last week. I don't mind waiting... good things take time. We'll hang ourselves tommorrow... unless Larry comes. And if he comes, we'll be saved. -- Mich

Re: Warnings, strict, and CPAN (Re: Closures and default lexical-scope for subs)

2001-02-21 Thread Peter Scott
Are we still having this discussion? :-) At 07:23 PM 2/21/01 -0500, [EMAIL PROTECTED] wrote: >Its true alot languages would consider many of Perl's warnings to be >errors, that's not really analgous to what we're talking about here. > >Run-time errors aren't quite in the same spirit as run-time w

Re: Warnings, strict, and CPAN (Re: Closures and default lexical-scopefor subs)

2001-02-21 Thread Sam Tregar
On Wed, 21 Feb 2001 [EMAIL PROTECTED] wrote: > On Wed, Feb 21, 2001 at 05:32:50PM -0500, Sam Tregar wrote: > > Examples? I know you're not talking about C or C++. I'm pretty sure > > you're not talking about Java - exception-handling renders the term "fatal > > error" almost meaningless. > > We

Re: End-of-scope actions: Toward a hybrid approach.

2001-02-21 Thread schwern
On Tue, Feb 20, 2001 at 02:19:18PM +, Simon Cozens wrote: > Sort of. What I really wanted to do was to be able to say > > sub foo { ... } > builtinify(foo); > > package bar; > foo(); # Refers to main::foo > package baz; > foo(); # Refers to main::foo > > (this is so that the forthcoming Saf

Re: Warnings, strict, and CPAN (Re: Closures and default lexical-scopefor subs)

2001-02-21 Thread Sam Tregar
On Wed, 21 Feb 2001, Bart Lateur wrote: > Actually, it's pretty common. Only, most languages are not as forgiving > as perl, and what is merely a warning in Perl, is a fatal error in those > languages. Trying to read the value of an uninitialized variable, for > example, that's commonly a fatal e

Re: Warnings, strict, and CPAN (Re: Closures and default lexical-scope for subs)

2001-02-21 Thread schwern
Has anyone actually used a language which has run-time warnings on by default? Or even know of one? -- Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/ Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One

Re: State of PDD 0

2001-02-21 Thread Ask Bjoern Hansen
On Tue, 20 Feb 2001, Ask Bjoern Hansen wrote: > I have created perl6-announce-pdd. Mail [EMAIL PROTECTED] > for clues. by the way, Adam Turoff was kind and volunteered to take the PDD archive pumpkin like he was handling the bazillion RFC's. [EMAIL PROTECTED] will thus go to him now. Be sure to