Front page | perl.perl5.porters |
Postings from September 2011
On 09/17/2011 11:12 AM, Rafael Garcia-Suarez wrote: > On 14 September 2011 16:58, Johan Vromans<jvromans@squirrel.nl> wrote: >> Dave Rolsky<autarch@urth.org> writes: >> >>> For additions of new features with new keywords, this use line will >>> block the new keywords from being usable in that scope. This seems >>> fairly easy, for some value of "fairly" and "easy" which I can't speak >>> to, since I've never hacked on the core C code ;) >> >> I've always wondered why the new keywords have not been added as "weak >> keywords" (like "lock"). This would have avoided the need for a >> feature pragma. > > In my mind that was to avoid effect at distance : if you upgrade a > module that changes its default export list to contain a sub named > like a weak keyword you're using, your program semantics changes under > you. > Does this mean this is an issue for 'lock' that should be documented? I don't see any other weak keywords mentioned in perlfunc. Are there any for which this should be documented?Thread Previous | Thread Next