KSL: moving forward
lk at teamten.com
Thu Mar 27 16:52:22 PDT 2008
> Certainly, I still have a sense that gathering as many language change
> implementations in a single place as possible is a good thing. Kijaro
> has achieved that without any great effort, and I suspect it will
> continue to do so.
I benefited tremendously from looking at your FCM code when I wrote
the list comprehension changes. I might even go so far as to say that
I would have given up without them. (I hit some pretty hard
roadblocks.) It was invaluable to be able to look at your changes (and
other branches of Kijaro) easily. In that respect I agree that it's
great to have all that in one place.
On the other hand, as an SVN project, how will Kijaro keep up with
OpenJDK changes? Do you plan to merge changes into the trunk manually?
(And then each of us into our branches?) Is there some automated
Mercurial-to-SVN bridge? Eventually you may be forced to adopt
Mercurial, at which point it's not clear what the Kirajo project even
is. Will it just host various dev branches within a single Mercurial
repository? Or multiple repositories? If compiler-dev is to be the
place where people announce projects, then Kijaro becomes just a place
to distribute repositories to third parties.
More information about the compiler-dev