in reply to Re: Constant names come into conflict with Perl style?
in thread Constant names come into conflict with Perl style?
All caps subs are reserved
Unfortunately, at some point last year the Perl 5 Porters accidentally broke this rule. There was a problem with cloning in threaded environments, and a magic subroutine named CLONE_SKIP was ushered in to deal with it.
Despite all the eyes of the people who worked on it, it escaped into the wild and it wasn't until a couple of months later that someone noticed that the name violated the guidelines (in that it really should have been called CLONESKIP).
Such is life.
• another intruder with the mooring in the heart of the Perl
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: Constant names come into conflict with Perl style?
by sgt (Deacon) on Feb 09, 2007 at 13:37 UTC |