[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl6-internals
Subject:    Re: call for readers II
From:       "register reg.ini" <register72 () gmail ! com>
Date:       2009-02-24 9:17:43
Message-ID: 4a80712f0902240117h76405717jaee956711bb07091 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


For what regards PIR I found that the contents in the docs/book toghether
with all the other documentation found in POD documents and on the website
is more than sufficient for getting the big picture about PIR. What I
would suggest is to give more visibility to the docs/book for example by a
direct citation/link in the PIR tutorial or somewhere else in a very visible
place in the Parrot website. I discovered the real value of the docs/book
only after  KJS pointed it to me as a valuable source of information.
I would like also to see much more on the internals of Parrot's calling
conventions. As it is today the book is outdated with the current status of
Parrot that only supports CPS calls. Furthermore I would like also to know
more of how CPS and parameters passing is implemented internally. While this
is not going to be useful to PIR users it is very interesting to better
understand Parrot architecture as a whole and it is essential knowledge to
people involved in JIT.
Just my 2 cents,
Register.

[Attachment #5 (text/html)]

<div>For what regards PIR I found that the contents in the docs/book toghet=
her with all the other documentation found in POD documents and on the webs=
ite is more than sufficient for getting the big picture about PIR. What I w=
ould=A0suggest is to give more visibility to the docs/book for example by a=
 direct citation/link in the PIR tutorial or somewhere else in a very visib=
le place in the Parrot=A0website. I discovered the=A0real value=A0of the do=
cs/book only=A0after =A0KJS pointed it to me as a valuable source of inform=
ation. </div>

<div>I would like also to see much more on the internals of Parrot&#39;s ca=
lling conventions. As it is today the book is outdated with the current sta=
tus of Parrot that only supports CPS calls.=A0Furthermore I would like also=
 to=A0know more of how CPS and parameters passing is implemented internally=
. While this is not going to be=A0useful to PIR users it is very interestin=
g to better understand Parrot architecture as a whole and it is essential k=
nowledge to people=A0involved in=A0JIT.</div>

<div>Just my 2 cents,</div>
<div>Register.</div>
<div>=A0</div>


_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev


[prev in list] [next in list] [prev in thread] [next in thread]