From: Alan Chen <alan@...>
Date: 2002-01-31T08:35:07+09:00
Subject: Re: Cardinal - project looking for a leader

I'm interested in working on this project, but have a time problem too
(paying work comes first :). In the past, I've worked in x86 Assembly
as well as "low-level" C, i.e. fiddling with link + execution level
executable headers, etc. I've also written small yacc/bison based
parser utilities which might help with the parsers (although there are
generally more capable compiler frameworks/toolkits out there now).

I might suggest an item nr 5.  Prototyping "hand-compiled" cases where
small snippets of ruby code are translated into parrot
bytecode/assembly. This give us some experience in how well the
current parrot vm might support ruby.

In terms of useless help :), I also have a project name change
suggestion, there's a species of parrot called the Eclectus parrot
whose coloration often features large patches of red in the male as
well as crimson in the female.

http://www.honoluluzoo.org/eclectus_parrot.htm

-- alan

On Thu, Jan 31, 2002 at 07:51:12AM +0900, Erik B?gfors wrote:
> Since I'm really interested in this project but I don't want to be a
> leader I'd like to say what I think are important and what a leader
> should need to think about.  This is all from my point of view.
> 
> The way I see it, there are four important areas to work with. 
> 1) The ruby in ruby parser 
> 2) The compiler to parrot bytecode 
> 3) The ruby-classes that needs to go into parrot 
> 4) Changes to parrot 
> 
> for nr 1) there are lot's of people working with this for different
> reasons, some not related to parrot.  I think this is great and I also
> think that we should use as much of that knowledge and information as
> possible but we should try to drive them in a "parrot-direction" just
> yet.  The people doing this is doing a great job I think. 
> 
> nr 2) This should take the information from the parser and generate
> parrot bytecode (of perhaps parrot assemby).  For this to work nr 3 have
> to be started.  I really don't see any reason to work with this just yet
> because things are too much in development right now. 
> 
> nr 3) This is what I've been working with a little.  I really think that
> parrot is great and I don't think there will be any problems doing this
> once parrot is in a state that make's doable.  Implementing classes is
> not at all hard and considering that parrot needs to provide regexp's,
> IO-handling and other low level stuff for all languages, we shouldn't
> have to deal to much with stuff like that (of course, they will not mind
> our help :) ). 
> 
> nr 4) This is were we should need someone who knows ruby by heart.  I
> know it's not me! :)  We need someone who is good at low level stuff and
> that can look into parrot and see if it's missing something that's
> important for ruby or if something simply is not right for ruby.  This
> should be done as soon as possible. 
> 
> So.  The question is how many people are interested in working with
> this.  I know I am but I'm not ready to take any kind of leader roll,
> and my knowledge is not good enough to work with some parts of this. 
> 
> I really think we need people for nr 4 and nr 3 now!  (nr 1 is already
> being worked on independently of ruby). 
> 
> Anyway, I'm really really exited about this project!
> 
> /Erik  
> 
> -- 
> Erik B?gfors               | http://www.ardendo.se/
> Erik.Bagfors@ardendo.se    | GSM +46 733 279 273
> fingerprint: 6666 A85B 95D3 D26B 296B 6C60 4F32 2C0B 693D 6E32
> 

-- 
Alan Chen
Digikata LLC
http://digikata.com