All the Perl that's Practical to Extract and Report

What's a name?

jonasbn on 2003-07-01T21:10:50

The other day I discovered that there is a module on CPAN called Clone, which does somewhat the same as my Object::Clone. So now I don't know which one to use for Metrics::LOC? Today I discovered there is a Perl module called Codebase, the name I had chosen for a series of modules, which I wanted to use for some codebase statistics.

...back to the drawing board or the idea box or...

cloning

nicholas on 2003-07-02T14:45:15

The other day I discovered that there is a module on CPAN called Clone, which does somewhat the same as my Object::Clone.
So now I don't know which one to use for Metrics::LOC?

None of the above. Storable dclone

  1. It's in the core as of 5.8
  2. It copies new features correctly (offhand I can think of restricted hashes, and hashes with UTF8 keys)
  3. It is well supported:
    $ perl -e 'use Clone qw(clone); $a = \$b; undef $a; $c = clone $a;'
    Segmentation fault

    That bug is 3 months old now and untouched, despite the fact that the fix is known

Re:cloning

jonasbn on 2003-07-06T15:55:24

Hmmm

My own Object::Clone does not suffer from the same problem, maybe it is because I use it in an strictly OOP way - it might have to require some more testing.

I will check out Storables dclone

switch units

jmm on 2003-07-02T19:36:17

code yours as Imperial::LOC

Re:switch units

jonasbn on 2003-07-06T14:50:28

Well the Metics::LOC name is availble, maybe I can find something more appropriate though :)