schwern@pobox.com wrote: > > > Command-line flags on by default [-T -Mstrict -Mwarnings]: > > We already beat this to death with the .perlrc discussion. You'll > break reams of Perl code you probably don't even know you have this > way. > > It destroys the portability of Perl programs. Yup, I agree. I actually was on the "this is a bad idea" side of the discussion the first time around. Just throwing it back out there. Not too sure about the whole -w on by default thing. Really makes me nervous. All I keep thinking about is the crap that Java spits out every two lines. Makes stuff really look unpolished, and the warnings change based on the JVM platform and version you're running. In Perl, this would create problems if new warnings are introduced later. All of a sudden scripts that have been working correctly now start spitting out warnings, and either you or your client is terribly confused. Maybe I just need some time to warm up to it, but it still makes me nervous... I think there's going to be so much stuff different in Perl 6 that the more similar we can make it to Perl 5 the better, otherwise we risk driving people running from the building. And this is one thing that seems like a "no brainer" for maintaining backwards-compat behavior... -Nate