On Sat, 22 Jul 2006 11:26:29 +0200, Johan Vromans wrote:

Hi Johan
I know I'm not entitled to say this, and it will make me even more
unpopular than I already am, but nevertheless I'm not going to
remain silent.
I fully support your speaking up.
I don't know all the inner details, but this M::B and version
dancing gives me the strong impression that something is terribly
wrong here at a fundamental design level.
Clearly something's wrong, but it may not be anything big, even though it's a
sort of show-stopper.
Dealing with version numbers is not quite trivial, but should be
fairly straightforward to deal with. I cannot (and for the time
being I refuse to) believe that it takes 651 releases (652 at the
time I write this) to get it right. Right!
I see that version.pm implements two flavours, a native perl
version and XS. Under the assumption that both versions are
functionally equal, I suggest to move the XS implementation to a
separate module and have version.pm be a single, straightforward
perl module that is easy to build, maintain, and to copy and paste
into a distribution if necessary. I cannot imagine that the gain in
Exactly. Ship a pure-Perl version immediately and stuff around with an XS
version off-line, so to speak. Pleeeeeeeeeeeeeeeeeeeaaaaaaaaaaassse!
efficiency is noticable for anything but an application that
processes thousands of version numbers, and in that case the

Everybody take a deep breath, and go back to basics!
Ron Savage, ron@savage.net.au on 22/07/2006
Let the record show: Microsoft is not an Australian company

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 4 of 33 | next ›
Discussion Overview
groupmodule-build @
postedJul 18, '06 at 12:16a
activeJul 26, '06 at 7:09a



site design / logo © 2018 Grokbase