On Thu, Oct 04, 2007 at 12:27:49PM -0700, Allison Randal wrote: > Patrick R. Michaud wrote: > >Slowly PGE and PGE::Perl6Regex are being updated to work with pdd15oo. > > What sort of changes do you end up making? It shouldn't touch anything > other than the lines of code creating a new class and instantiating a > new object. (And really, it shouldn't even touch creating a new class.) > If it's more work than that, it may be something I need to change in the > implementation.
I've also been using this as an opportunity to convert things like 'PGE::Match' into ['PGE';'Match'], so that we get the "true nested namespaces model" that is given in the namespaces pdd. Parrot's old object system didn't really have sufficient support for this, whereas the new one does. It did occur to me this morning that we can stick with the flat-namespace model that PGE and other tools have been using up-to-now, and make the switch to using multilevel namespaces sometime later. Either way there's going to be a big conversion cycle involved somewhere, and it has an impact on all of the compiler tools and languages that use them. > I'd rather not add any more dependencies to releasing the new object > model. I'll happily look at the diffs to Perl6Rexex and duplicate the > changes in P6Regex. It's not just P6Regex, but also the pgc.pir and Perl6Grammar compilers that are impacted. > We can mark P6Regex as deprecated and have languages shift over to > Perl6Regex, I just don't want to wait for all those language changes > before merging the branch back in. Based on earlier IRC discussions, I'm already marking P6Regex as deprecated. I should've done that months ago, since it's clear it's not the way things are going. But if we stick to the use of flat namespaces, we can keep it around a little while longer. Your choice. :-) Pm
