in reply to RFC: Transactions.pm

Even though it doesn't have DBIx in the name, it still cannot begin with a lowercase letter. It probably shouldn't be a top-level name anyway.

But, the module czars will tell you that.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

Replies are listed 'Best First'.
Re: •Re: RFC: transactions.pm
by Juerd (Abbot) on Apr 27, 2003 at 13:30 UTC

    Even though it doesn't have DBIx in the name, it still cannot begin with a lowercase letter.

    Very good point.

    It probably shouldn't be a top-level name anyway.

    I couldn't find an existing namespace to fit it in.

    Currently, I think Transactions is a good name. If anyone has a better name, let me know. Please keep it short, because "use Transactions" can be used as a sort of select if you use multiple transaction capable objects.

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

Re: RFC: transactions.pm
by Abigail-II (Bishop) on Apr 27, 2003 at 22:45 UTC
    It "cannot" begin with a lowercase letter? Why is that?

    Abigail

        Then pray tell me, what is a pragma? I mean, if constant.pm is a pragma, why can't a module supplying transaction support not consider itself a pragma?

        And who's deciding whether you "get to use lowercase"? I uploaded a module with an all lowercase name in the past, and noone stepped forward with a big "We don't allow you to do that, nanananana" sign. Perl, CPAN and PAUSE all handle it fine.

        Abigail

        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' }