[perl #23115] powerpc linux support

2003-07-24 Thread Arcady Goldmints
# New Ticket Created by "Arcady Goldmints" # Please include the string: [perl #23115] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=23115 > Contrary to popular belief, linux does run on things other than x86, and people wi

Re: approaching python

2003-07-24 Thread Benjamin Goldberg
K Stol wrote: > > - Original Message - > From: "Michal Wallace" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, July 23, 2003 4:48 PM > Subject: approaching python > > > > > Hey all, > > > > I've been thinking about the "compiling python to > > parrot" concept. Right now

Slightly foolish question... :)

2003-07-24 Thread Benjamin Goldberg
What kind of semantics do we want for perl6, if we have: my $fh1 = fdopen( $n ); do { my $fh2 = fdopen( $n ); }; # is $fh1 valid or not at this point? For that matter, what about: for(1..2) { my $fh = fdopen( $n ); # does this succed the second time? } Should thes

Re: Events

2003-07-24 Thread Damien Neil
On Tue, Jul 22, 2003 at 11:41:25PM -0400, Dan Sugalski wrote: > First, to get it out of the way, I don't have to convince you of > anything. You have to convince me. For better or worse I'm > responsible for the design and its ultimately my decision. If you > don't want async IO, it's time to ma

Re: approaching python

2003-07-24 Thread Joseph F. Ryan
Luke Palmer wrote: >Klass-Jan Stol writes: > >>>The thing is, I don't have a lot of experience when it comes to >>>compilers, but I do know a whole lot about python. :) If this >>>approach makes sense, is there someone with IMCC experience who'd >>>be willing to do some virtual pair programming wi

Re: [COMMIT] Parrot emits an executable

2003-07-24 Thread Simon Glover
It now builds and tests fine. Simon

Re: [COMMIT] Parrot emits an executable

2003-07-24 Thread Daniel Grunblatt
On Thursday 24 July 2003 16:13, Simon Glover wrote: > On Thu, 24 Jul 2003, Daniel Grunblatt wrote: > > On Thursday 24 July 2003 15:55, Juergen Boemmels wrote: > > > Magic: 7f 45 4c 46 01 01 01 > > > > 00 > > -- > > 00 00 00 00 00 00 00 00 > > > > > OS/ABI:UNIX - Sy

Re: [COMMIT] Parrot emits an executable

2003-07-24 Thread Simon Glover
On Thu, 24 Jul 2003, Daniel Grunblatt wrote: > On Thursday 24 July 2003 15:55, Juergen Boemmels wrote: > > Magic: 7f 45 4c 46 01 01 01 > 00 > -- > 00 00 00 00 00 00 00 00 > > > OS/ABI:UNIX - System V > > Patch is in, please resync and try it. > It's now dieing

Re: approaching python

2003-07-24 Thread Michal Wallace
On Thu, 24 Jul 2003, Joseph F. Ryan wrote: > I'm not familiar with the Python bytecode spec (to be a little more > accurate, I'm completely clueless about it), but perhaps something > similar can be done? Also, another thing to consider is that it > might be easier to translate python bytecode d

Re: [COMMIT] Parrot emits an executable

2003-07-24 Thread Daniel Grunblatt
On Thursday 24 July 2003 15:55, Juergen Boemmels wrote: > Magic: 7f 45 4c 46 01 01 01 00 -- 00 00 00 00 00 00 00 00 > OS/ABI:UNIX - System V Patch is in, please resync and try it. > boe Daniel

Re: approaching python

2003-07-24 Thread Michal Wallace
On 24 Jul 2003, Luke Palmer wrote: > Klass-Jan Stol writes: > > module, right? I don't know Python, and I've a little experience > > with IMC, but it seems to me only a new code generator module should ...[snip] > Well... sortof. It's definitely going to take writing a whole new > code generato

Re: [COMMIT] Parrot emits an executable

2003-07-24 Thread Juergen Boemmels
Daniel Grunblatt <[EMAIL PROTECTED]> writes: > On Thursday 24 July 2003 15:14, Simon Glover wrote: > > On Thu, 24 Jul 2003, Daniel Grunblatt wrote: > > > I have checked in a first attempt to make parrot generate an executable. > > > > > > It works fine on x86 - OpenBSD/linux/FreeBSD and should als

Re: [COMMIT] Parrot emits an executable

2003-07-24 Thread Daniel Grunblatt
On Thursday 24 July 2003 15:48, Juergen Boemmels wrote: > Daniel Grunblatt <[EMAIL PROTECTED]> writes: > > I have checked in a first attempt to make parrot generate an executable. > > This is very cool. Thanks. > > > It works fine on x86 - OpenBSD/linux/FreeBSD and should also work on > > NetBSD >

Re: [COMMIT] Parrot emits an executable

2003-07-24 Thread Daniel Grunblatt
On Thursday 24 July 2003 15:14, Simon Glover wrote: > On Thu, 24 Jul 2003, Daniel Grunblatt wrote: > > I have checked in a first attempt to make parrot generate an executable. > > > > It works fine on x86 - OpenBSD/linux/FreeBSD and should also work on > > NetBSD > > It's not working for me on Lin

Re: [COMMIT] Parrot emits an executable

2003-07-24 Thread Juergen Boemmels
Index: exec.c === RCS file: /cvs/public/parrot/exec.c,v retrieving revision 1.1 diff -u -r1.1 exec.c --- exec.c 24 Jul 2003 17:18:30 - 1.1 +++ exec.c 24 Jul 2003 18:45:22 - @@ -12,7 +12,9 @@ */ #include -#include +#if HA

Re: [COMMIT] Parrot emits an executable

2003-07-24 Thread Simon Glover
On Thu, 24 Jul 2003, Daniel Grunblatt wrote: > I have checked in a first attempt to make parrot generate an executable. > > It works fine on x86 - OpenBSD/linux/FreeBSD and should also work on NetBSD It's not working for me on Linux/x86 -- the build is failing with: In file included from exe

[COMMIT] Parrot emits an executable

2003-07-24 Thread Daniel Grunblatt
I have checked in a first attempt to make parrot generate an executable. It works fine on x86 - OpenBSD/linux/FreeBSD and should also work on NetBSD For PPC (Darwin) it generates code correctly just for programs that use *only* fully jitted opcodes. It should work with or without JIT_CGP. Afte

Re: io.t test failure

2003-07-24 Thread Juergen Boemmels
Simon Glover <[EMAIL PROTECTED]> writes: > Test number 6 in io.t is failing on a number of the tinderboxes with > a double-free error. > > Test 6 does this: > > open P0, "temp.file", "<" > clone P1, P0 > read S0, P1, 1024 > print S0 > end > > And the clone function in th

Re: [perl #23025] [PATCH] env.t doesn't test the env ops on solaris (and others)

2003-07-24 Thread Lars Balker Rasmussen
Benjamin Goldberg <[EMAIL PROTECTED]> writes: > Lars Balker Rasmussen wrote: >> However, now the 4th test fails on Solaris (and most likely other OS's >> witout setenv/unsetenv). This is because the test relies on a key >> disappearing from %ENV when it's been unsetenv'ed - this doesn't >> happen

Re: approaching python

2003-07-24 Thread Christian Renz
to link with python, we should probably write our own parser.[1] Just use Perl 6 to write it :). Ooops... looks like a chicken-and-egg problem... Greetings, Christian

Re: approaching python

2003-07-24 Thread K Stol
- Original Message - From: "Luke Palmer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, July 24, 2003 2:22 AM Subject: Re: approaching python > Klass-Jan Stol writes: > > > The thing is, I don't have a lot of experience when it co

Re: approaching python

2003-07-24 Thread Luke Palmer
Klass-Jan Stol writes: > > The thing is, I don't have a lot of experience when it comes to > > compilers, but I do know a whole lot about python. :) If this > > approach makes sense, is there someone with IMCC experience who'd > > be willing to do some virtual pair programming with me and spike > >

Re: approaching python

2003-07-24 Thread K Stol
- Original Message - From: "Michal Wallace" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 23, 2003 4:48 PM Subject: approaching python > > Hey all, > > I've been thinking about the "compiling python to > parrot" concept. Right now it looks like the > approach is to st

RE: Events

2003-07-24 Thread Brad Schick
From: Dan Sugalski [mailto:[EMAIL PROTECTED] > We are going to do all I/O under the hood asynchronously. > Completed async IO puts an event in the event queue... I am new to parrot, but I've had plenty of experience with (non-unix) I/O systems. Having a totally async core in Parrot is pretty clea