At 10:01 AM -0700 10/10/02, Ramesh Ananthakrishnan wrote:
>Hi,
> Most systems, have a variety of scripting languages
>to do stuff in. And almost all the time to make it
>work with another library you have to specifically
>port the other library to a specific interpreter.
>Which means you have separate binding for each
>language. gtk has separate bindings for perl, python
>and ruby.
> Is it possible to avoid this with parrot?
That's one of the main points, yep. You write one library, it works
with all Parrot-hosted libraries.
> Which brings me to another er... ramble. The
>documents there are about Parrot aren't very easy for
>novices.
Currently they're not meant to be--they're internals documentation
geared at the folks writing the interpreter, but we do need to get
less technical documentation, and some's being worked on. More, of
course, is always welcome. :)
> Novice that I am I'd be willing to write a
>few "really from the ground up how to do stuff" sort
>of introductory guide to extending languages to Parrot
>or extending toolkits to it. Er.. anybody else
>intrested? Can get me going...
Absolutely. We've not got the extension mechanism spec'd out quite
fully enough, I think, though Brent's done some prelim work on it.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
