Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Jun 19 13:15:02 2006 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with
No more svn commits please.
Thanks,
leo
Am Montag, 19. Juni 2006 15:35 schrieb Leopold Toetsch:
No more svn commits please.
Release done!
leo
On Jun 18, 2006, at 2:02, Vishal Soni via RT wrote:
I am just wonedring if it would make sense to seperate out code for
each
supported operating system under a directory structure. At the time
of build the specific code for target operating system is added to the
source tree.
Yep.
On behalf of the Parrot team I'm proud to announce another
monthly release of Parrot.
I'd like to thank all involved people as well as our
sponsors for supporting us.
What is Parrot?
Parrot is a virtual machine aimed at running Perl6 and other dynamic
languages, see http://www.parrotcode.org/
Hi Leo,
So do we need to change os.pmc to leverage this infrastructure and get rid
of the platform specific code( currently implemented via IFDEF) from os.pmc?
-Vishal
On 6/19/06, Leopold Toetsch [EMAIL PROTECTED] wrote:
On Jun 18, 2006, at 2:02, Vishal Soni via RT wrote:
I am just
On Jun 19, 2006, at 19:30, Vishal Soni wrote:
So do we need to change os.pmc to leverage this infrastructure and get
rid of the platform specific code( currently implemented via IFDEF)
from os.pmc?
I think that all platform-specific code should be factored out, i.e.
the existing methods
Hi Leo,
That sounds great. One quick question would it make sense to start defining
a generic platform interface that that all supported platforms need to
implement. A quick example of a similar abstraction would be the Apache
Portable Runtime (http://apr.apache.org/).
Let me know what your
