Randy W. Sims wrote:
I don't believe the current version objects support mathematical
operations, but it seems something very reasonable to add. (At least,
the addition of increment($step)/decrement($step) type ops.)
I'm fairly adamant that version.pm is feature-complete; I don't want to add
John Peacock [EMAIL PROTECTED] writes:
I'm fairly adamant that version.pm is feature-complete; I don't want
to add *anything* else to the base class. I am planning on releasing
version::Math which will cover what you discuss, though. I have been
playing with it for a couple of years, on a
On 4/16/07, Johan Vromans [EMAIL PROTECTED] wrote:
John Peacock [EMAIL PROTECTED] writes:
Especially now since you mention version::Math, an ordinary module in
a pragma's namespace?
Original issue aside, I think there is an assumption that we can add
new functionality that is pragma related
Johan Vromans wrote:
Sorry to bring this up (again) but I am still wondering why version is
a pragma instead of a module.
The original goal was to make the simple act of writing:
$VERSION = 1.2.0;
create a version object. It turns out I can do that in bleadperl (since
I have
Johan Vromans wrote:
I'd say this is the VERY LAST CHANCE to change it. Once released as a
core module with 5.10 there is no way back.
I'd say that boat has already pulled out of the dock and is rapidly
making its way through the North Atlantic! Damian's Perl Best
Practices recommends 'use
John Peacock [EMAIL PROTECTED] writes:
Damian's Perl Best
Practices recommends 'use version' in print (since July 2005), so I
don't think we /can/ change it now...
Damian recommends truck loads of CPAN modules. But that doesn't
necessarily mean that it has to be put in the core that way.
--
On Apr 15, 2007, at 7:48 AM, Marvin Humphrey wrote:
On Apr 15, 2007, at 2:41 AM, Eric Wilhelm wrote:
What's that for?
use Carp; BEGIN{ $SIG{__DIE__} = \carp::confess }
If we can do without it, we probably should.
Looks like debugging code (giving you a stack trace rather than a 1
