Re: Whats next?

> > So where I can get a more detailed plan of the structure of uuu?
> > Whats the next task to do? Can it be done without hours and hours of
> > reading other peoples code (to understand how everything works so far)?
> 
> You can read the code. There really is no way around it; the brief
> description is on the webpage and the detailed one is in the code. There
> really isn't much to it, though, so maybe it won't take you hours and
> hours.

Okay, I'll try my best 

> > I read, maybe uuu wont always use python. What does that mean?
> > Why not python? Are there other candidates?
> 
> Tweaking the standard interpreter has been a pain. Maybe focus will
> shift to developing some language ideas I've had, or maybe I'll take a
> closer look at erlang or e or eiffel or something like that. (Why do
> these languages all start with "e"?) That would imply progress though,
> and there hasn't been much of that lately.

I dont know if you know about it, but maybe also Gwydion Dylan would be
considerable since it is interpretable as well as binary compileable
(at the moment thru c).
If you want to take a look: http://www.gwydiondylan.org

--

-- 
"Windows is a 64 bit tweak of a 32-bit extension to a 16-bit user
interface for an 8-bit operating system based on a 4-bit architecture
from a 2-bit company that can't stand 1 bit of competition."