[perl #27246] [PATCH] Correct ommision in config/gen/makefiles/befunge.in

# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #27246] # in the subject line of all future correspondence about this issue. # http://rt.perl.org:80/rt3/Ticket/Display.html?id=27246 > There was no PERL = ${perl} definition in this file (which does exist i

[perl #27243] [PATCH] Corrects (?) misleading POD & usage re: -C option.

# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #27243] # in the subject line of all future correspondence about this issue. # http://rt.perl.org:80/rt3/Ticket/Display.html?id=27243 > Changes 2 lines (marked ** below) in t\harness to correct errors in the POD and

Re: Current PLATFORMS

* Leopold Toetsch ([EMAIL PROTECTED]) [040228 23:59]: > Paul Cochrane <[EMAIL PROTECTED]> wrote: > > Hi, > > > I got parrot to build on Alpha OSF1, but I can't get make test to go. Here's > > what I see: > > > rolf:[524]/var/tmp/parrot>/usr/bin/make test > > perl t/harness --gc-debug --running-m

Re: [PATCH] Configure test for inet_aton

On Friday, February 27, 2004, at 12:26 , Andrew Dougherty wrote: On Fri, 27 Feb 2004, Gordon Henriksen wrote: inet_pton is preferrable, as it supports IPv6. That is, inet_pton should trump inet_aton if both are available. Probably, but that would require testing to see if inet_pton is available

Re: PLATFORM

On Sat, 2004-02-28 at 03:43, Leopold Toetsch wrote: > CGoto core: make testg testC Both of these worked on Linux PPC with gcc-3.2.3 I did see an intermittent hang, this time on the second test of t/src/intlist.t. killall -HUP intlist_2 made the test continue, though it failed. > JIT:m

Re: PLATFORM

On Sat, 2004-02-28 at 06:43, Leopold Toetsch wrote: > Kenneth A Graves <[EMAIL PROTECTED]> wrote: > > On Fri, 2004-02-27 at 16:08, Kenneth A Graves wrote: > >> > >> How do I verify which runloops/features are working? > > CGoto core: make testg testC Both give: All tests successful, 1 test and 61

Re: Exegesis 7: Overflow Fields

I also don't expect $x = ''; $y = " $x "; to assign '' to $y either, but that's the equlvalent of what you say form() will do. I see your point. I was more worried about arrays of items some of which are empty strings and having items disappear out my repost because form() throws them aw

Re: Exegesis 7: Literal '{' in format string

Would that need to be a double backslash in a double-quoted string, or is there some new Perl 6 magic that keep it from being needed? No, it would need to be a double backslash in a qq{..} string. Fortunately qq{..} strings are very rarely needed in Cs. Damian

Re: Exegesis 7: Overflow Fields

Damian Conway wrote: But that means I have to pre-process data lists that just happen to contain empty strings so that they won't disappear on me. Huh? An empty string already *has* disappeared on you. ;-) > This seems to violate least surprise. I'd be much more surprised if an empty string *

Re: Exegesis 7: Overflow Fields

But that means I have to pre-process data lists that just happen to contain empty strings so that they won't disappear on me. Huh? An empty string already *has* disappeared on you. ;-) > This seems to violate least surprise. I'd be much more surprised if an empty string *didn't* disappear. After

Re: Exegesis 7: Literal '{' in format string

Damian Conway wrote: Joe Gottman asked: How do you put a literal '{' or '}' into a format string in Perl 6? Do you use a backslash? Yes, a backslash will quote anything (including backslash). Note that you really only need to backslash '{', since '}' isn't special by itself. Would that need to be

Removing a lexical

Is there a way to "unstore" a lexical in a scope? -- Will "Coke" Coledawill at coleda dot com

Re: Exegesis 7: Overflow Fields

Damian Conway wrote: Mark A. Biggar wrote: What if I want to interpolate an empty string and let the fill characters work? Then you interpolate a single fill character instead of the empty string. But that means I have to pre-process data lists that just happen to contain empty strings so that

Re: Exegesis 7: Literal '{' in format string

Joe Gottman asked: How do you put a literal '{' or '}' into a format string in Perl 6? Do you use a backslash? Yes, a backslash will quote anything (including backslash). Note that you really only need to backslash '{', since '}' isn't special by itself. Damian

Exegesis 7: Literal '{' in format string

How do you put a literal '{' or '}' into a format string in Perl 6? Do you use a backslash? Joe Gottman

Re: Exegesis 7: Overflow Fields

Mark A. Biggar wrote: What if I want to interpolate an empty string and let the fill characters work? Then you interpolate a single fill character instead of the empty string. Damian

Re: Exegesis 7: Miscellany

Smylers asked: * What happens if an undefined format is passed to C? I'm presuming (and hoping) that's a run-time error. Currently treated as "", with internal warnings. Probably should throw an exception. * In 'What a block art though...' (page 2) I don't think there's supposed to

Re: Thinking about Accessors

On Sun, Feb 29, 2004 at 01:44:47PM -0500, Aaron Sherman wrote: : On Fri, 2004-02-27 at 21:57, Luke Palmer wrote: : : > method bar_attr() will get { $.bar_attr } : > will set { $.bar_attr = $_ } : : I'm confused by this in only one way... since method bar_attr and the : a

Re: Release done

On Sun, Feb 29, 2004 at 05:36:22PM +0100, Leopold Toetsch wrote: > Currently working on 10a of RELEASE_INSTRUCTIONS everything should be > done, so let the checkins begin. Woohoo! Well done. I see it's all over use.perl now too. Nicholas Clark

Re: Whither Apocalypse 7?

Dave, I had the same problem you did, if I understand you correctly. Eventually, I found the document I believe people are discussing. I'd tell you how, but I don't recall. See the forward below my signature for what I found. Best wishes, George of Oakland.pm -- Forwarded Message

Re: Whither Apocalypse 7?

[EMAIL PROTECTED] (Dave Mitchell) writes: > Did I miss something? Was there ever an apocalyse 7? Yes, there was. It was tacked on the end of Apocalypse 6, and said essentially "No longer in core. See Damian." -- DYSFUNCTION: The Only Consistent Feature of All of Your Dissatisfying Relati

Re: Whither Apocalypse 7?

On Sat, 2004-02-28 at 14:08, Dave Mitchell wrote: > Did I miss something? Was there ever an apocalyse 7? > Also, why aren't the apocalyses and excegises announced on any of the p6 > lists (like, er, perl6-announce for example)? I suspect that Damian is waiting on finalizing the modules mentioned i

Re: Thinking about Accessors

On Fri, 2004-02-27 at 21:57, Luke Palmer wrote: > method bar_attr() will get { $.bar_attr } > will set { $.bar_attr = $_ } I'm confused by this in only one way... since method bar_attr and the accessor bar_attr have the same name, how do I write an accessor that recurses

Whither Apocalypse 7?

Did I miss something? Was there ever an apocalyse 7? Also, why aren't the apocalyses and excegises announced on any of the p6 lists (like, er, perl6-announce for example)? Yours grumpily, Dave. -- My get-up-and-go just got up and went.

Release done

Currently working on 10a of RELEASE_INSTRUCTIONS everything should be done, so let the checkins begin. Have fun, leo

Parrot 0.1.0 Released

Parrot 0.1.0 "Leaping Kakapo" Released! The Parrot team proudly presents the Parrot 0.1.0 leap release. It provides some milestones like objects and multi-threading1[1] and supports many more platforms. After some pause you can grab it from

Re: Please no checkins

Jens Rieks <[EMAIL PROTECTED]> wrote: > Hi leo, > Am Sonntag, 29. Februar 2004 11:47 schrieb Leopold Toetsch: >> I'm currently preparing 0.1.0, so please no changes to CVS until further >> ntice. > Here is the tetris example, include it if you want... Sorry, too late. Next time. > jens leo

Re: Please no checkins

tetris.tgz Description: application/tgz

Re: Please no checkins

Hi leo, Am Sonntag, 29. Februar 2004 11:47 schrieb Leopold Toetsch: > I'm currently preparing 0.1.0, so please no changes to CVS until further > ntice. Here is the tetris example, include it if you want... > Thanks, > leo jens

i386 JIT problem with set_i_n

Hi, the following test gives wrong results on i386/JIT. It looks like the set_i_n JIT op rounds the number, whereas the non JIT OP does not round the number. jens output_is(<<'CODE', <<'OUT', "set_i_n testing"); ##PIR## .sub _main .local num n .local int i n = 1.4 i = n prin

Re: www.parrotcode.org

On 29 Feb 2004, at 03:07, Robert Spier wrote: [...] Someone else can take care of this for him. (And I know he'd love it if someone stepped forward to become official web content maintainer.) We'll provide that person with resources and support, and it'll be quite fun and easy for everyone. Well

Please no checkins

I'm currently preparing 0.1.0, so please no changes to CVS until further ntice. Thanks, leo

Re: Inconsistent Parrot / IMCC behavior

Melvin Smith <[EMAIL PROTECTED]> wrote: > At 08:01 PM 2/28/2004 -0800, Gregor N. Purdy wrote: >>I made the change, and now I get consistent results. I'll check that in. >> >>I am still not clear, though, on why we wouldn't have the same failure >>in all cases. I'd think these should be equivalent: