Adam Kennedy wrote: > John Peacock wrote: >> Adam Kennedy wrote: >>> What does this mean for bugs though? >> >> But that's true of any new features of v5.10.0 that cannot be >> backported to >> maintperl. > > But what's true? :)
I mean that *any* new feature introduced in v5.10.0 could have bugs that might require the release of v5.10.1 in order to fix. We haven't gotten to the point of being able to treat the core Perl as if it were a collection of independently updated modules (other than the few dual life modules). For example, a problem with Perl's tokenizer or regex engine cannot be fixed with a CPAN release. That's the level at which version objects are integrated in the core files. The fact that I can *also* provide that code as a CPAN compatibility module is a valuable feature. > You are in a differing position to most features, in the you could end > up working on all versions of Perl EXCEPT a growing range from 5.10.0 > upwards. No, the file version.pm is a noop under v5.10.0 because exactly the same code already exists in the Perl core itself (not as a bundled module). The same C code in the CPAN release is already in the C code used to build Perl. > Is what you are saying that the Perl version still works, and we can > later choose to upgrade the pure Perl version over the top of, say, the > 5.10.0 version? No, because the pure Perl release is merely a rewrite in Perl of the XS code which is already part of the Perl v5.10.0 core (in universal.c and util.c). The XS/C code is the reference implementation; it would not be desirable to use the pure Perl implementation, since that is just a later rewrite. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Blvd Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747