Melvin Smith [EMAIL PROTECTED] writes:
In the past couple of years we've seen several sub-projects pop-up
and subsequently fizzle out (maybe due to Parrot slow
progress or maybe due to lack of critical mass).
I propose creating 'parrot-compilers' as a general
purpose list for any and all
On Mon, Nov 17, 2003 at 08:58:17PM +, Pete Lomax wrote:
I think this would be a *very* cool thing.
What he said.
Pete
idem
--
stef
Melvin Smith [EMAIL PROTECTED] wrote:
I propose creating 'parrot-compilers' as a general
purpose list for any and all language development
As long as traffic on p6i is as low as current, I don't see the need for
another list.
-Melvin
leo
---BeginMessage---
I
Think this would be cool, and I will help.
my research masters is retargetting gcj to parrot.
I am only a month into it so I have not put up a project page yet.
On Tuesday 18 November 2003 00:04, Joseph Ryan wrote:
Pete Lomax wrote:
On Mon, 17 Nov 2003 11:35:51 -0800,
At 01:50 PM 11/18/2003 +0100, Leopold Toetsch wrote:
Melvin Smith [EMAIL PROTECTED] wrote:
I propose creating 'parrot-compilers' as a general
purpose list for any and all language development
As long as traffic on p6i is as low as current, I don't see the need for
another list.
I'm concerned
On Nov 17, 2003, at 11:22 AM, Melvin Smith wrote:
In the past couple of years we've seen several sub-projects pop-up
and subsequently fizzle out (maybe due to Parrot slow
progress or maybe due to lack of critical mass).
I propose creating 'parrot-compilers' as a general
purpose list for any and
On Tue, 18 Nov 2003, Jeff Clites wrote:
On Nov 17, 2003, at 11:22 AM, Melvin Smith wrote:
In the past couple of years we've seen several sub-projects pop-up
and subsequently fizzle out (maybe due to Parrot slow
progress or maybe due to lack of critical mass).
I propose creating
The reason I think parrot-compilers would be useful, is that its
dedicated to helping people (like me) write compilers for parrot,
whereas (in my understanding), perl6-internals@ is really about the
development of the vm itself (I would subscribe to both). I see
parrot-compilers@ as opening
On Nov 18, 2003, at 9:07 AM, Sterling Hughes wrote:
The reason I think parrot-compilers would be useful, is that its
dedicated to helping people (like me) write compilers for parrot,
whereas (in my understanding), perl6-internals@ is really about the
development of the vm itself (I would
Sterling Hughes wrote:
The reason I think parrot-compilers would be useful, is that its
dedicated to helping people (like me) write compilers for parrot,
whereas (in my understanding), perl6-internals@ is really about the
development of the vm itself (I would subscribe to both). I see
In the past couple of years we've seen several sub-projects pop-up
and subsequently fizzle out (maybe due to Parrot slow
progress or maybe due to lack of critical mass).
I propose creating 'parrot-compilers' as a general
purpose list for any and all language development
(until an appropriate time
Melvin Smith wrote:
In the past couple of years we've seen several sub-projects pop-up
and subsequently fizzle out (maybe due to Parrot slow
progress or maybe due to lack of critical mass).
I propose creating 'parrot-compilers' as a general
purpose list for any and all language development
(until
On Mon, 17 Nov 2003 11:35:51 -0800, Sterling Hughes
[EMAIL PROTECTED] wrote:
I think this would be a *very* cool thing.
What he said.
Pete
Pete
http://palacebuilders.pwp.blueyonder.co.uk/euphoria.html
Pete Lomax wrote:
On Mon, 17 Nov 2003 11:35:51 -0800, Sterling Hughes
[EMAIL PROTECTED] wrote:
I think this would be a *very* cool thing.
What he said.
Ditto.
- Joe
14 matches
Mail list logo
