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

2001-02-22 Thread Dan Sugalski
At 10:48 AM 2/22/2001 +0100, Bart Lateur wrote: >On Wed, 21 Feb 2001 17:32:50 -0500 (EST), Sam Tregar wrote: > > >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

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

2001-02-22 Thread Paul Marquess
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] ... > > The basic usefulness of warnings is not in question. This is about > the *perception* of their utility. Warnings are only useful if the > user heeds them. The question is, will having them on by default make > the user more or less l

Re: Things have paused... really?

2001-02-22 Thread Kirrily Robert
In lists.projects.perl.meta, you wrote: >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.

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

2001-02-22 Thread David Grove
Peter Scott <[EMAIL PROTECTED]> wrote: > At 09:36 AM 2/22/2001 +, David Grove wrote: > >This is what's scaring me about all this talk about > >exceptions... it can break this mold and make Perl into a "complainer > >language" belching up uncaught (don't care) exceptions forcing try/excep

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

2001-02-22 Thread Peter Scott
At 09:36 AM 2/22/2001 +, David Grove wrote: >This is what's scaring me about all this talk about >exceptions... it can break this mold and make Perl into a "complainer >language" belching up uncaught (don't care) exceptions forcing try/except >blocks around every piece of IO or DB handling. Th

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

2001-02-22 Thread David Grove
Bart Lateur <[EMAIL PROTECTED]> wrote: > On Wed, 21 Feb 2001 17:32:50 -0500 (EST), Sam Tregar wrote: > > >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

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

2001-02-22 Thread John Porter
Sam Tregar wrote: > [EMAIL PROTECTED] wrote: > > Well, an unhandled exception in Java is death for the program. > > Yup. So all (potentially) exceptions are "fatal errors"? Well, that > definition fits "almost meaningless" pretty well, in my opinion! Not exactly. Java defines two clases of "t

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

2001-02-22 Thread Bart Lateur
On Wed, 21 Feb 2001 17:32:50 -0500 (EST), Sam Tregar wrote: >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. >Examples? I know you're no

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

2001-02-22 Thread Bart Lateur
On Wed, 21 Feb 2001 16:01:39 -0500, [EMAIL PROTECTED] wrote: >Has anyone actually used a language which has run-time warnings on by >default? Or even know of one? 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 er

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

2001-02-22 Thread schwern
On Wed, Feb 21, 2001 at 06:05:25PM -0800, Peter Scott wrote: > Are we still having this discussion? :-) *sigh* yes. > I do not think there is hard dividing line between warnings and > errors. "Unable to establish network connection - saving file to local > disk" means the program is still ru