On Thu, Feb 15, 2001 at 02:40:52PM -0600, Jonathan Scott Duff wrote: > On Thu, Feb 15, 2001 at 12:25:44PM -0800, Edward Peschko wrote: > > well, I was thinking about this - there really should be an extra switch that > > makes this possible, rather than typing 'no strict; no warn;' ie: > > > > #!/usr/local/bin/perl -q # for quick and dirty. > > We already have a switch that means "quick and dirty", it's called > "-e" Beautiful. then just co-opt it. Right now when I say: #!/usr/local/bin/perl -e in a file i get Can't emulate -e on #! line at a.p. Either that, or add '-q' as a file version for '-e'. And in any case, make '-e' have the additional connotation that implies 'no strict', and 'no warn'. Seems simple enough to me. Ed
- Re: Closures and default lexical-scope for subs Randal L. Schwartz
- Re: Closures and default lexical-scope for subs Branden
- Re: Closures and default lexical-scope for subs John Porter
- Re: Closures and default lexical-scope for subs abigail
- Re: Closures and default lexical-scope for subs abigail
- Re: Closures and default lexical-scope for subs Nicholas Clark
- Re: Closures and default lexical-scope for subs Edward Peschko
- Re: Closures and default lexical-scope for subs Jonathan Scott Duff
- Re: Closures and default lexical-scope for subs Edward Peschko
- Re: Closures and default lexical-scope for subs Peter Scott
- Re: Closures and default lexical-scope for subs Nathan Wiger
- Re: Closures and default lexical-scope for subs Edward Peschko
- Re: Closures and default lexical-scope for subs Peter Scott
- Re: Closures and default lexical-scope for subs Edward Peschko
- Re: Closures and default lexical-scope for subs abigail
- Re: Closures and default lexical-scope for subs Nicholas Clark
- Re: Closures and default lexical-scope for subs Edward Peschko
- Re: Closures and default lexical-scope for subs abigail