Front page | perl.perl5.porters |
Postings from August 2010
On Fri, Aug 6, 2010 at 2:00 PM, karl williamson <public@khwilliamson.com> wrote: > Perhaps people more familiar with the nuances of Perl will see more. The > output follows (note that cmp, ge, and x would be forbidden under our new > policy): > > Pre-existing potential conflicts: cmp, cos, exec, exp, ge, m, pipe, pop, > pos, s , semop, x > > New potential conflicts: close, else, grep, lc, le, log, or, our, sleep, > splice , uc, use, xor > > New potential conflicts with /t: exists, exit, getc, getpgrp, gmtime, goto, > gt, msgget, oct, reset, semget, setpgrp, sort, tie, time, times, tr > > New potential conflicts with /d: die, do, ord, redo, rmdir I'm not sure all of these are real conflicts. Since s/// and m// are expressions, wouldn't anything after them have to be another operator or else a statement modifier? I think that cuts it down a lot. DavidThread Previous | Thread Next