Andrew Whitworth wrote:
On Fri, Apr 10, 2009 at 6:15 AM, register reg.ini <[email protected]> wrote:
Are you going to add a chapter on Parrot's internals? I am thinking
about some material that could be more useful to people interested directly
in the development of Parrot rather than people involved in the development
of languages for the VM.
Especially something about the implementation of calling convections would
be very interesting.
Now might be a slightly different time though, and it might be a good
idea to write up some of the design information somewhere to tell
people how parrot works internally and why we've made the design
decisions that we have. Also, serious discussions of the internal
architecture are going to be necessary for people who are interesting
in writing NCI wrappers, extensions, dynpmcs, dynops, etc, and that's
a target audience that we are very much going to want to focus on for
the advent of Parrot 2.0.
Given that the information is useful to write out in book form,
whether that information belongs in this particular book or not is
another question entirely: The majority of this book is targeted at
end users, not core hackers. A better idea would probably be to start
drafting a separate "Parrot Internals" book, instead of cramming the
information into this "Parrot Users Guide" one we already have.
This is the "Parrot Developer's Guide". And, yes, we probably will add a
chapter (or two or three) on the internals in a later edition. For this
edition I'm focused on helping language developers get off the ground,
since that's the group we're most looking to grow this year.
We will certainly release an updated edition with 2.0.
Allison
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
