Re: Event handling (was Re: [CVS ci] exceptions-6: signals, catch a SIGFPE (generic platform)

2003-09-12 Thread Mark A. Biggar
Nicholas Clark wrote: On Thu, Jul 17, 2003 at 08:40:44PM -0400, Benjamin Goldberg wrote: Actually, I'm thinking of something like the following... suppose the original code is like: label_foo: loop body branch_address: branch label_foo Add in the following: e_handler_foo: .local Perl

Re: Event handling (was Re: [CVS ci] exceptions-6: signals, catch a SIGFPE (generic platform)

2003-09-12 Thread Nicholas Clark
On Thu, Jul 17, 2003 at 08:40:44PM -0400, Benjamin Goldberg wrote: > Actually, I'm thinking of something like the following... suppose the > original code is like: > >label_foo: >loop body >branch_address: >branch label_foo > > Add in the following: > >e_handler_foo: >.l

Re: [PATH] Get rid of very annoying header warnings on darwin

2003-09-12 Thread Nicholas Clark
On Fri, Sep 12, 2003 at 10:54:27PM +0100, Nicholas Clark wrote: > I think it's still fractionally broken, in that -Wno-format will > erase -Wformat-nonliteral A suitable anchor seemed to fix that. Nicholas Clark

Re: [PATH] Get rid of very annoying header warnings on darwin

2003-09-12 Thread Nicholas Clark
On Fri, Sep 12, 2003 at 12:57:45PM +0100, Arthur Bergman wrote: > > On Thursday, September 11, 2003, at 07:50 pm, Brent Dax wrote: > > > Arthur Bergman: > > # This gets rid of the very annoying long double might change warning > > # under Darwin... > > > > Thanks, applied (config/init/hints/darw

Re: Macro arguments themselves

2003-09-12 Thread Austin Hastings
--- Luke Palmer <[EMAIL PROTECTED]> wrote: > Alex Burr writes: > > But I confidently predict that no-one with write a useful > > partial evaluator for perl6. The language is simply too big. > > Then again, there are some very talented people with a lot of free > time in the Perl community; I wou

Re: Macro arguments themselves

2003-09-12 Thread Mark A. Biggar
Alex Burr wrote: [EMAIL PROTECTED] (Luke Palmer) writes: I would hope the former. However, what about this compile-time integral power macro[1]? macro power ($x, $p) { if $p > 0 { { $x * power($x, $p-1) } } else { { 1 } } } That would hopef

Re: Macro arguments themselves

2003-09-12 Thread Luke Palmer
Alex Burr writes: > In theory you could write one as a perl6 macro, although it would be > more convenient if there was someway of obtaining the syntax tree of a > previously defined function other than quoting it (unless I've missed > that?). There is a large class of cool optimizations possibl

Re: Subject: Macro arguments themselve

2003-09-12 Thread Alex Burr
[EMAIL PROTECTED] (Luke Palmer) writes: > I would hope the former. However, what about this compile-time > integral power macro[1]? > > macro power ($x, $p) { > if $p > 0 { > { $x * power($x, $p-1) } > } > else { > { 1 } > } > } > >

Re: Macro arguments themselves

2003-09-12 Thread Alex Burr
[EMAIL PROTECTED] (Luke Palmer) writes: > I would hope the former. However, what about this compile-time > integral power macro[1]? > > macro power ($x, $p) { > if $p > 0 { > { $x * power($x, $p-1) } > } > else { > { 1 } > } > } >

Re: [PATH] Get rid of very annoying header warnings on darwin

2003-09-12 Thread Arthur Bergman
On Thursday, September 11, 2003, at 07:50 pm, Brent Dax wrote: Arthur Bergman: # This gets rid of the very annoying long double might change warning # under Darwin... Thanks, applied (config/init/hints/darwin.pl version 1.7). However, can you see if the diff below my sig (applied against 1.7, no

Re: Make test failures with CVS parrot under Electric Fence.

2003-09-12 Thread ndronen
On Fri, Sep 12, 2003 at 10:53:20AM +0200, Leopold Toetsch wrote: > [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi, > > > I built a fresh CVS parrot with garbage collection and linked parrot > > and imcc against Electric Fence. A few tests failed. The (edited) > > results are here: > > >

Re: Make test failures with CVS parrot under Electric Fence.

2003-09-12 Thread Leopold Toetsch
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi, > I built a fresh CVS parrot with garbage collection and linked parrot > and imcc against Electric Fence. A few tests failed. The (edited) > results are here: > Core was generated by `./parrot --gc-debug t/op/interp_6.pasm'. > Core was

Re: [RFT] File Spec

2003-09-12 Thread Leopold Toetsch
Michael G Schwern <[EMAIL PROTECTED]> wrote: > People make mistakes. Perhaps you should produce some errors if a user > strays outside these rules. Garbage in, garbage out: Bad. Garbage in, > error out: Good. Albeit I did write, we need a simple interface to get at runtime libs and includes, I