parrotbug: Can it handle attachments?

2007-08-12 Thread James E Keenan
docs/submissions.pod states: "DO NOT paste the content of the new file or files into the body of the message." I.e., send the content as an email attachment. But whenever I have used the 'parrotbug' utility, I have never seen a way to send an attachment. I have always had to past the content

Interfacing parrot with the new Java Scripting API

2007-08-12 Thread Tim Bunce
Could someone familar with parrot take a look at the Java Scripting API (aka JSR223) and let us know how much work would be involved in adding support for it to parrot? See https://scripting.dev.java.net/ and http://java.sun.com/javase/6/docs/technotes/guides/scripting/index.html Something to wat

[perl #44567] Undefined arrayref in MethodEmitter.pm

2007-08-12 Thread via RT
# New Ticket Created by Bob Rogers # Please include the string: [perl #44567] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44567 > I find the following patch necessary to build PMCs in r20605. I'm using Perl 5.8.1, so

Re: [perl #44567] Undefined arrayref in MethodEmitter.pm

2007-08-12 Thread Bob Rogers
From: "James Keenan via RT" <[EMAIL PROTECTED]> Date: Sun, 12 Aug 2007 10:05:16 -0700 I don't know much about MethodEmitter.pm, so I don't have any preferences. I think tewk has done most of the recent work in this area, so he may have a preference. kid51 Maybe we should als

Re: [perl #44567] Undefined arrayref in MethodEmitter.pm

2007-08-12 Thread James E Keenan
Bob Rogers wrote: So far, such values have not been observed, and would probably indicate that something was broken upstream. Do you have a preference for letting these fail hard? I don't know much about MethodEmitter.pm, so I don't have any preferences. I think tewk has done most of t

Re: [perl #44567] Undefined arrayref in MethodEmitter.pm

2007-08-12 Thread chromatic
On Saturday 11 August 2007 07:57:55 Bob Rogers wrote: >I find the following patch necessary to build PMCs in r20605. I'm > using Perl 5.8.1, so it may be that newer Perls autovivify differently. > This changed since r20358, but I'm not sure it's worth tracking down. > If I hear no objections,

Re: Fixing warn_unused_result

2007-08-12 Thread James E Keenan
Andy Lester wrote: I don't have a gcc 3.3 anywhere. Any of you got one I can get to? Wouldn't the first place to try be: http://www.gnu.org/software/gcc/gcc-3.3/

Re: [perl #44567] Undefined arrayref in MethodEmitter.pm

2007-08-12 Thread Bob Rogers
From: "James Keenan via RT" <[EMAIL PROTECTED]> Date: Sun, 12 Aug 2007 08:55:25 -0700 Your commit statement says: + $decs is not always defined, at least in older Perls. However, your patch required that $decs be not merely defined, but true: +$decorators = $decs && le

Re: [perl #44567] Undefined arrayref in MethodEmitter.pm

2007-08-12 Thread James E Keenan
Bob Rogers wrote: # New Ticket Created by Bob Rogers # Please include the string: [perl #44567] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=44567 > I find the following patch necessary to build PMCs in r20605. I'm

Re: [perl #44553] [PATCH] Add a new PIR tutorial for defined

2007-08-12 Thread Paul Cochrane
On 11/08/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote: > On Sat, Aug 11, 2007 at 05:00:33PM +0200, Paul Cochrane wrote: > > > Within the past few months we've standardized on always quoting > > > type names in PIR, so the above needs to read > > > > > > $P1 = new 'String' > > > > > > Throug