Hi All,
We've been thinking long and hard about Parrot and found that
the spec viz packfile versions , code segmentations, opcodes and
virtually everything is changing minute to minute ...
So we think it might do good to have a Parrot-dev'r do the
co-ordination duties . What I had in mind was a guy who said to us
"hey folks, the packfile has changed .. refer pod" whenever some
serious change happened. As well as review the opcodes needed for
C# like some sort of i2f or something and report an RFC for that..
I would like to know if anyone would like to ensure that the
two projects remain in constant communication about standards,
specs and stuff...
Also to finish up with a question, how is the perl6 compiler
built ?. A brief look at Tree.pm left me wondering ... it looks
almost like a manual version of treecc code ,with all the sub's
representing operations::names...(just comparing to cscc design,
so that we can keep track of changes to both easily....).
Cheers,
Gopal
--
The difference between insanity and genius is measured by success
