Hi All,
I am currently embarking on a project to create a new language. Right now
I'm in the process of selecting the platform that's going to give me the
best starting point.
My first choice is whether to go for a VM, or a C-Python style
implementation. Right now I'm leaning towards VM.
The lan
> > My big requirement is for lightweight microthreads...
>
> Parrot's going to live on top of the system thread library, so you may run
> into some issues that way. Not all systems can handle lots of
> threads--many of them (including Linux) have very low limits relative to
> what most microthread
> > But Parrot has continuations. Doesn't this gives me (cooperative)
> > microthreads? (with a little work on my part).
>
> Sure...
So these would be real cheap right? Time and space overheads similar to
regular procedure calls?
> The world could also use a pony. And a lollypop. :)
Um, I think
Hi Michal
> > My first choice is whether to go for a VM, or a C-Python style
> > implementation. Right now I'm leaning towards VM.
>
> I'm not sure what you mean by the difference here. CPython
> does have a VM, it's just a stack-based one.
OK so I'm learning already :)
I thought CPython was mor
OK, here's what I'm hoping Parrot can provide for the language I'm building.
My big requirement is for lightweight microthreads (hopefully *very*
lightweight - I'm considering one scheduler that can handle *millions* of
threads on a single machine). Oh and I will need them to be serializable. I
ca
Hi All
Is there somewhere you can point me to a discussion about the choice for a
register VM rather than a stack VM? If not, let's have it now - I'll
volunteer to tidy the end result into a postable form.
The FAQ briefly mentions:
we're already running with a faster opcode dispatch
than
