HTTP/2 200 cache-control: max-age=43200 server: Combust/Plack (Perl) vary: Accept-Encoding content-encoding: gzip content-length: 2104 content-type: text/html; charset=utf-8 last-modified: Sat, 11 Oct 2025 15:46:02 GMT traceparent: 43b215eb2c5132cd6b68c1dbaf258c99 strict-transport-security: max-age=15768000 Front page | perl.perl5.porters | Postings from July 2008

Re: Creative and *routine* use of so-called

Thread Previous

On approximately 7/30/2008 10:09 AM, came the following characters from 
the keyboard of Ben Morrow:
> Quoth perl@NevCal.com (Glenn Linderman):
>> <SAFE_ARGV> and <MAGIC_ARGV> sound fine for explicit use.
> 
> Core keywords don't have underscores in.
Fine.  I don't care about the spelling, just the concept.  It is not 
clear to me that we even need actual syntax for <SAFE_ARGV> and 
<MAGIC_ARGV>, just the concepts.  <> can be actually used in the code, 
once the appropriate semantics have been selected.  At least I 
personally cannot imagine a need for both sets of semantics in the same 
program; every time I try, I think the results of such an attempt would 
be confusing at best, and error-prone at worst, and a documentation 
nightmare.  Once a particular semantic has been chosen, it could be 
irreversible, as far as I am concerned.
>> A pragma or pragma parameter should exist to enable <> to have the 
>> behavior of <SAFE_ARGV>, and avoid the above warning.
> 
> Both <SAFE_ARGV> and *ARGV = *SAFE_ARGV for default behaviour can be
> done with a module, so it should be.
I don't care about the spelling, just the concept.  Having a warning by 
default, and a way to turn it off and enable the safe function.
>> A pragma or pragma parameter should exist to enable <> to have the 
>> behavior of <MAGIC_ARGV> with its v1-v5.10 semantics, and avoid the 
>> above warning.  This pragma or pragma parameter could be placed on CPAN 
>> so that authors using/expecting <> to be <MAGIC_ARGV> can have create 
>> code that is portable across versions; use of other pragma parameters 
>> would not be supported by v5.10 or older.
> 
> This pragma already exists: no warnings 'argv'. Possibly warnings would
> have to be dual-lifed with knowledge of new warning categories.
That could be used, yes.  In any case, whatever is used would have to be 
available on CPAN to provide the ability to write portable code, so that 
in 5.12 there is a way to have the warning by default, and a way to 
enable the magic function, that also can be made to work in older 
versions of perl.
> Ben
-- 
Glenn -- https://nevcal.com/
===========================
A protocol is complete when there is nothing left to remove.
-- Stuart Cheshire, Apple Computer, regarding Zero Configuration Networking

Thread Previous

• Re: Creative and *routine* use of so-called by Ed Avis
• Re: Creative and *routine* use of so-called by Aristotle Pagaltzis
• Re: Creative and *routine* use of so-called by Ed Avis
• Re: Creative and *routine* use of so-called by Glenn Linderman
• Re: Creative and *routine* use of so-called by Ben Morrow
• Re: Creative and *routine* use of so-called by Glenn Linderman