David Wheeler wrote:
On Apr 16, 2005, at 3:00 PM, Adam Kennedy wrote:
It's going to totally depend on what you want to wrap around it...
Do you want the human interacty mode? Or the machine county mode.
"machine county mode"? Just that, I think.
Forget the document object for a moment, you are mor
What I'm moving towards is what SVK does. It has an SVK::Version module
which simply defines $SVK::VERSION. Then in other modules you can write:
use SVK::Version; our $VERSION = $SVK::VERSION;
That way it will be picked up by most $VERSION scanners.
See my post further up about syncron
> I've yet to read anything /really/ convincing for either side -
so I'd do whatever you're comfortable with myself.
In my case I tend to use synchronised version numbers. For big APIs (20+
classes) I often use Class::Autouse to recursively load them.
If two subsequent versions of the dist chang
David Cantrell wrote:
Adrian Howard wrote:
On 18 Apr 2005, at 17:03, David Cantrell wrote:
Number::Phone::UK::Data - no version, this is where the .0004 comes from
though. It has no version number because the
entire file is generated from a *real
Adrian Howard wrote:
On 19 Apr 2005, at 11:40, David Cantrell wrote:
The script that generates it doesn't change. The data that it mangles
into a module is the bit that changes.
Can you add a version number to the data?
Yep, did that last night. It's (eg) 1.20050420.
I dug through my mail and fo
