Simon Cozens:
# Burl Nyswonger:
# > The ability to build the VM in an extremely stripped-down
# configuration
# > would be really useful for embedded environments (where you
# only have, say
# > a 4MB flash that must hold a kernel, all libs, apps, etc...).
#
# By the time Parrot's ready to be
Burl Nyswonger:
> The ability to build the VM in an extremely stripped-down configuration
> would be really useful for embedded environments (where you only have, say
> a 4MB flash that must hold a kernel, all libs, apps, etc...).
By the time Parrot's ready to be embedded, memory prices will hav
>EVERYONE: Should we have a PARROT_TINY_CORE define you can activate to
>cut some of this stuff out?
Yes. I like the idea.
-Melvin
Burl Nyswonger:
# I am concerned with the size of parrot recently --
# libparrot.so is like
# 650K, and libparrot.a is like 770K. This is stripped and
# without JIT (and
# there is a lot more to come, right?)
Actually, I'm not sure there's much left. More portable bytecode
formats, an extension
I am concerned with the size of parrot recently -- libparrot.so is like
650K, and libparrot.a is like 770K. This is stripped and without JIT (and
there is a lot more to come, right?)
The ability to build the VM in an extremely stripped-down configuration
would be really useful for embedded envi
