Re: [Oopic-compiler-devel] Reverse-engineering the OOpicMK compiler--preliminary

[Neil D. <nd...@us...>]

Andrew Porrett wrote:
> At 09:42 PM 4/29/2004 -0400, D. Daniel McGlothin wrote:
> >> >> I wonder if the codes are identical across all target hardware types.
> >> >
> >> >It seems so. The differences in hardware seem to be additional
> >> >byte-codes/firmware capability as the OOpic revision 'increases'.
> >>
> >> So it's easy then.  Is it done yet?  :)
> >
> >
> >I sheepishly grin and and then blurt "but I'm working on the landscaping and
> >garden just now."
> >
> >
> >BTW,  what form should this information be submitted?  Sourceforge DOCS,
> >e-mail attaches, or what?
> >
> >Daniel
> 
> No, I mean so the _whole_ compiler project is easy then.  :)
> 
> (so is it done yet?)

I had half an hour to kill earlier, so I finished the whole project off,
just for kicks.  But then I accidentally deleted the folder containing all
the code.  Sorry about that...

> As far as forms go, I'm a simple ASCII .txt kinda guy, but .doc's,
> spreadsheets, .html's, whatever are OK with me.

I'm a simple ASCII guy too (meaning I'm a simple guy, and I like ASCII!),
and ASCII ensures that anyone can read it, regardless of platform.  You
never know when another developer might want to join in.

> Email attachments are convenient, since they just show up by themselves
> without any extra effort on my part.  Since this is such a small team, I
> think we can start off rather informally and just email stuff back and
> forth for now.

Agreed, although anything we're collectively working on, collaboratively,
might be better done via the site, otherwise we'll just spend all our time
throwing attachments at each other and fixing up the differences.  But
files just one of us is working on, or files sent just for reading,
attachments sound like the way to go.

Once we get onto actual source code, I guess CVS is the way to go...

Note that the mailing list currently has a 40kb limit for postings,
although I believe we can increase this if necessary.

Neil
-- 
Neil Durant
<nd...@us...>