in reply to •Re: Re: RFC: transactions.pm
in thread RFC: Transactions.pm

Those are reserved for pragmata.

Not reserved. They're used for pragmata, but not reserved.

If you're not a P5P patch generating person, you don't get to use lowercase. {grin}

Anyone can have lc'ed module names. For pragma-ish modules, it's a good idea to use lowercase module names. load, forks and my own again are well chosen names, in my opinion.

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

Replies are listed 'Best First'.
Re: Re: •Re: Re: RFC: transactions.pm
by grantm (Parson) on Apr 27, 2003 at 23:52 UTC
    Not reserved. They're used for pragmata, but not reserved.
    perlmodlib.pod and perlstyle.pod:
    "Perl informally reserves lowercase module names for 'pragma' modules like integer and strict."
    perltoot.pod:
    "You can look at other object-based, struct-like overrides of core functions in the 5.004 release of Perl in File::stat, Net::hostent, Net::netent, Net::protoent, Net::servent, Time::gmtime, Time::localtime, User::grent, and User::pwent. These modules have a final component that's all lowercase, by convention reserved for compiler pragmas, because they affect the compilation and change a builtin function."

    "Reserved by convention" is arguably a contradiction, but it looks like lower case names are OK as long as you use a namespace that starts with upper case - say for example DBIx:: :-)