This is a cross-over from perl6-language.
First off, I'd like to make it clear that I'm *not* arguing against
the advantages of having strict and warnings on. I turn them on for
every program I write (except strict for one-liners) and strongly
advocate that everyone else do the same. However,
I'm moving this over to perl6-language-strict.
On Fri, Feb 16, 2001 at 03:48:22PM -0800, Edward Peschko wrote:
> Why? Its not the filename, its how its used -
>
> require("A"); # library - strict, warnings on
> use A;# library - strict, warnings on
> do "A"# li
On Fri, Feb 16, 2001 at 03:28:36PM -0800, Edward Peschko wrote:
> Its because '-w' is a global switch.
What about the new lexical warnings? "use warnings"?
> > I'm not sure what you mean by a policy. Do you mean you want people
> > to have to say C explicitly? Do you want to
> > make it a co
On Fri, Feb 16, 2001 at 06:08:20PM -0800, Peter Scott wrote:
> >Come to think of it, what language or popular compiler does have
> >run-time (not compile-time) warnings on by default?
>
> Er, Perl is loose enough that those run-time warnings substitute for only a
> part of the kind of strictness
On Fri, Feb 16, 2001 at 06:22:45PM -0800, Edward Peschko wrote:
> On Fri, Feb 16, 2001 at 08:41:02PM -0500, [EMAIL PROTECTED] wrote:
> > On Fri, Feb 16, 2001 at 03:28:36PM -0800, Edward Peschko wrote:
> > > Its because '-w' is a global switch.
> >
> > What about the new lexical warnings? "use wa
On Fri, Feb 16, 2001 at 06:52:22PM -0800, Peter Scott wrote:
> S'not about saving keystrokes, as many times as I do type the same things
> in every file; it's about giving newbies the right introduction to the
> language and providing appropriate feedback at the appropriate level of
> individua
I think we're rapidly approaching "agree to disagree" territory here.
On Fri, Feb 16, 2001 at 09:03:54PM -0800, Edward Peschko wrote:
> Right now, I do a search on the standard distribution, and I see
> 'use warnings::register' in 13 out of 270 modules. Make 'use warnings' the
> default, and y
On Fri, Feb 16, 2001 at 10:45:27PM -0800, Peter Scott wrote:
> Help me out here. You're saying:
User: perl -w myprogram.pl
Perl: Name "main::x" used only once: possible typo at -e line 1.
Use of uninitialized value in division (/) at myprogram.pl line 5.
Use of uninitialized v
On Sat, Feb 17, 2001 at 11:09:29AM -0800, Peter Scott wrote:
> >No, there will probably be a big push to shut it off, based on
> >historical reactions to this sort of thing.
>
> Maybe I'm missing something; I'm sure the philosophy is for the standard
> distribution to be -w clean, so shouldn't e
On Sat, Feb 17, 2001 at 01:31:27PM -0800, Edward Peschko wrote:
> > I thought that was the problem you were having. Forgetting to type
> > "use strict" in your programs.
>
> No -- its *anywhere* that you write scripts/modules/what have you. Anywhere
> you miss it, it is a syntax error to me.
I
On Sat, Feb 17, 2001 at 05:28:51PM -0800, Peter Scott wrote:
> Why this difference depending on whether I reference a module with an
> absolute path or a relative one?
That's very, umm... interesting. Hmm. Post it to p5p, see what happens.
On Sun, Feb 18, 2001 at 04:45:46AM +, Simon Cozens wrote:
> On Sat, Feb 17, 2001 at 05:00:51PM -0800, Peter Scott wrote:
> > Simon Cozens submitted a patch which failed the test
>
> ...and MJD and Jarkko and I worked on it and we put together something
> which was OK.
Both Simon's and Peter'
On Sun, Feb 18, 2001 at 02:16:21PM -0800, Edward Peschko wrote:
> The things you mention are procedural. And as tempting as it is to enforce a
> little vigor on procedure, I agree with you. I don't want to make a coding
> architecture on by default..
The decision to write tests and docs is proce
. Programs
will still run the same (baring Deep Mucking with $SIG{__WARN__}).
So I say, sure! Let's give it a shot and see what happens. I hope it
turns out that I'm wrong and Ed is right.
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality
ing a colossal waste of disk space, this isn't much
better (probably worse) than just remembering to use -w and C.
It destroys the portability of Perl programs.
--
Michael G Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
le of a fight, you don't want your fire computer to crash.
Asserts use this sort of philosophy, which is why they have an NDEBUG
flag which allows you to shut them off program-wide.
PERL_BATTLE_MODE environment variable anyone? ;)
--
Michael G. Schwern <[EMAIL PROTECTED]>http:/
very far yet.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Do you actually think about what you are saying or is it an improvisational
game of Mad Libs that you play in your head?
17 matches
Mail list logo
