Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jonasbn (1153)

  reversethis-{gro.napc} {ta} {nbsanoj}
AOL IM: BJonasN (Add Buddy, Send Message)

Perl Programmer located in Copenhagen, Denmark. Active member of Copenhagen Perl Mongers.

Author of:

  • Business::DK::CPR
  • Business::DK::CVR
  • Business::DK::PO
  • Business::OnlinePayment::CashCow
  • Date::Holidays
  • Date::Holidays::Abstract
  • Date::Holidays::Super
  • Date::Pregnancy
  • Games::Bingo
  • Games::Bingo::Bot
  • Games::Bingo::Print
  • Module::Info::File
  • Module::Template::Setup
  • Test::Timer

and maintainer of:

  • Tie::Tools
  • XML::Conf
  • Workflow

Journal of jonasbn (1153)

Thursday February 09, 2006
05:36 AM

CPAN candidates in CVS - part 2

[ #28632 ]

I mailed the perl.module-authors list to get some feedback.

Here is the mail:


I am considering releasing some modules I use for work to CPAN.

The modules are implementing general (simple) algorithms for dealing with
verification and generation of some simple code systems used in Denmark,
yes they are very local.

My question is what namespace would be relevant for this?

I have some suggestions?

- Business::DK::*
- Algorithm::DK::*

Algorithm seems like the more general one, but since it is not hard
science simply modulus gymnastics and it is not security, but mere
validation and generation.

The codes in question are:

CVR, tax/company code/identifier
CPR, personal code/identifier
PO, postal order code/identifier

These validations and generations are mostly interesting to companies etc,
hence the suggestion for Business::DK::*.

Looking forward to getting some feedback,


It came to me that the Busienss::* namespace might be the proper place and also more easily digested by the namespace police (well I guess we are all namespace police to some extent).

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.