[perl #42225] [BUG] t/codingstd/c_parens.t getting false negatives

2007-03-31 Thread Paul Cochrane via RT
On Fri Mar 30 21:31:53 2007, [EMAIL PROTECTED] wrote: On Fri Mar 30 21:03:36 2007, [EMAIL PROTECTED] wrote: While I haven't fixed it, I've mitigated it a fair amount. The original version has 273 failing files. My painfully simple fix drops that to 130. My fix is just instead of

[perl #42218] [PATCH][Cygwin] Use bc on Cygwin

2007-03-31 Thread via RT
# New Ticket Created by Ron Blaschke # Please include the string: [perl #42218] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42218 Attached patch enables bc on Cygwin (if available). Also, if bc is skipped

Re: [perl #37997] r10604 build failure on Cygwin

2007-03-31 Thread Eric Hanchrow
Ron == Ron Blaschke [EMAIL PROTECTED] writes: Ron Sorry, I guess there was some mental PATH overloading going Ron on. Try adding the absolute path to Fblib/lib to PATH. Ron export PATH=/path/to/parrot/blib/lib:$PATH Ron And then make. OK, that gets me past that failure,

[perl #42236] [PATCH] Codingstd/whitespace fixes (keyword one-space open-paren)

2007-03-31 Thread Paul Cochrane via RT
On Fri Mar 30 23:36:45 2007, [EMAIL PROTECTED] wrote: Hi, I'm bored, so I'm going through and fixing some failing tests in t/codingstd/ At the moment I'm working on c_parens.t. Here's one that fixes the majority of the failures in the first third of the tests, which looks that code

[perl #42082] [BUG]: Configure.pl: Misspecified option; 2 non-valid options documented

2007-03-31 Thread James Keenan via RT
Applied in r17899.

[perl #42082] [BUG]: Configure.pl: Misspecified option; 2 non-valid options documented

2007-03-31 Thread James Keenan via RT
Closing ticket.

Re: [perl #42074] [PATCH] add RECURSION_LIMIT macro

2007-03-31 Thread Leopold Toetsch
Am Samstag, 31. März 2007 00:23 schrieb Paul Cochrane: It would be pretty simple to make this a settable/queryable interpreter property. Would that be valuable? It's already a gettable interpreter property (interp-recursion_limit). I'm guessing it would be valuable to be able to set the

[svn:parrot-pdd] r17907 - trunk/docs/pdds/draft

2007-03-31 Thread allison
Author: allison Date: Sat Mar 31 12:09:18 2007 New Revision: 17907 Modified: trunk/docs/pdds/draft/pdd15_objects.pod Log: [pdd]: Integrating some questions and comments on the Objects PDD. Modified: trunk/docs/pdds/draft/pdd15_objects.pod

Re: [perl #42074] [PATCH] add RECURSION_LIMIT macro

2007-03-31 Thread Allison Randal
Alek Storm wrote: Hmm. You know what I just found out? The ParrotInterpreter PMC doesn't implement set_pmc_keyed. Any objections to implementing it? Pass. It has methods, and access to the internal data of the interpreter object should go through those methods. Allison

Re: [perl #42074] [PATCH] add RECURSION_LIMIT macro

2007-03-31 Thread Alek Storm
On 3/31/07, Allison Randal [EMAIL PROTECTED] wrote: Alek Storm wrote: Hmm. You know what I just found out? The ParrotInterpreter PMC doesn't implement set_pmc_keyed. Any objections to implementing it? Pass. It has methods, and access to the internal data of the interpreter object should

Re: Syntax for Constructing new Objects (and classes?)

2007-03-31 Thread Alek Storm
$P0 = get_hll_namespace $P1 = $P0.find_class(HLLClass) $P2 = $P1.new() Will new() be a vtable method or PCCMETHOD in a Class PMC? That's the only way I can see this syntax not conflicting with normal method-calling syntax.

Re: [perl #42074] [PATCH] add RECURSION_LIMIT macro

2007-03-31 Thread Allison Randal
Alek Storm wrote: Do you mean a PCCMETHOD? If we're just getting and setting attributes, I really think we should be using getattribute and setattribute, or getprop and setprop, instead of expanding the ParrotInterpreter namespace with a bunch of simple getter and setter methods.

Re: Syntax for Constructing new Objects (and classes?)

2007-03-31 Thread Jonathan Worthington
Allison Randal wrote: No dot-prefix, but also no bareword class names. Only quoted names. Same is true for both high-level objects and low-level PMC objects. I guess the upshot of this is we need to deprecate the old syntax and make sure the new one works. Deprecate in the next release, remove

Re: Syntax for Constructing new Objects (and classes?)

2007-03-31 Thread Allison Randal
Alek Storm wrote: $P0 = get_hll_namespace $P1 = $P0.find_class(HLLClass) $P2 = $P1.new() Will new() be a vtable method or PCCMETHOD in a Class PMC? That's the only way I can see this syntax not conflicting with normal method-calling syntax. new() is a class method, an ordinary method on

Re: [svn:parrot-pdd] r17907 - trunk/docs/pdds/draft

2007-03-31 Thread Jonathan Worthington
[EMAIL PROTECTED] wrote: Adds a single attribute to the class. It takes a simple string name and, optionally, a simple string value for type. {{ Conjectural: Actually, the -simple string value alone won't cut it. We need to take a key there too? }} +simple string value alone won't cut it. We

Re: Syntax for Constructing new Objects (and classes?)

2007-03-31 Thread Allison Randal
Jonathan Worthington wrote: Allison Randal wrote: No dot-prefix, but also no bareword class names. Only quoted names. Same is true for both high-level objects and low-level PMC objects. I guess the upshot of this is we need to deprecate the old syntax and make sure the new one works. Deprecate

Re: Syntax for Constructing new Objects (and classes?)

2007-03-31 Thread Alek Storm
Thank you, but I know what a PCCMETHOD is. On 3/31/07, Allison Randal [EMAIL PROTECTED] wrote: Alek Storm wrote: $P0 = get_hll_namespace $P1 = $P0.find_class(HLLClass) $P2 = $P1.new() Will new() be a vtable method or PCCMETHOD in a Class PMC? That's the only way I can see this syntax

Re: Syntax for Constructing new Objects (and classes?)

2007-03-31 Thread chromatic
On Saturday 31 March 2007 12:42, Alek Storm wrote: $P0 = get_hll_namespace $P1 = $P0.find_class(HLLClass) $P2 = $P1.new() Will new() be a vtable method or PCCMETHOD in a Class PMC? That's the only way I can see this syntax not conflicting with normal method-calling syntax. I believe

Re: [svn:parrot-pdd] r17907 - trunk/docs/pdds/draft

2007-03-31 Thread Allison Randal
Jonathan Worthington wrote: But names of types need to also be specifiable as keys for full flexibility? Since they may be in any namespace, not just the current one. Fair enough. But I'll be very clear that using a key to specify a type is *not* the same thing as using a key to specify a

Re: compilers/pirc continued...

2007-03-31 Thread Allison Randal
Klaas-Jan Stol wrote: Another idea: I heard on #parrot that 'bcg' is a project to create an api for emitting bytecode. Maybe it's an idea to have a look at how good it would fit compilers/pirc? Seems like a sensible path to explore. Allison

[perl #42254] [BUG] Broken I/O on missing file

2007-03-31 Thread via RT
# New Ticket Created by Ron Blaschke # Please include the string: [perl #42254] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42254 This showed up on Cygwin, but is most likely a problem on other platforms too.

[perl #42261] Extensive failures in t/compilers/imcc/imcpasm/*.t and t/pmc/sub.t

2007-03-31 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #42261] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42261 Failures in 'make test', reproduced via 'prove -v'. Please see attached.

Re: [perl #42169] [CAGE] Create a sample subversion/config

2007-03-31 Thread Allison Randal
Paul Cochrane wrote: ala recent IRC discussion... thread on parrot-porters and put it in the repository in a likely place. and mention it in the committer docs. It should conform to and be referred to by the standards in the file_metadata.t test. How does this look (following)? It's

[svn:parrot-pdd] r17913 - trunk/docs/pdds/draft

2007-03-31 Thread allison
Author: allison Date: Sat Mar 31 19:06:39 2007 New Revision: 17913 Modified: trunk/docs/pdds/draft/pdd15_objects.pod Log: [pdd]: A few more small tweaks to Objects PDD. Modified: trunk/docs/pdds/draft/pdd15_objects.pod

[svn:parrot-pdd] r17914 - trunk/docs/pdds/draft

2007-03-31 Thread allison
Author: allison Date: Sat Mar 31 20:41:43 2007 New Revision: 17914 Modified: trunk/docs/pdds/draft/pdd04_datatypes.pod Log: [pdd]: Move the monolithic list of vtable names where it belongs: in the Datatypes PDD. Modified: trunk/docs/pdds/draft/pdd04_datatypes.pod

[svn:parrot-pdd] r17915 - trunk/docs/pdds/draft

2007-03-31 Thread allison
Author: allison Date: Sat Mar 31 23:49:02 2007 New Revision: 17915 Modified: trunk/docs/pdds/draft/pdd15_objects.pod Log: [pdd]: A more extensive set of revisions to the Objects PDD. Modified: trunk/docs/pdds/draft/pdd15_objects.pod

[perl #42045] [PATCH] add return statement to clone in iterator.pmc

2007-03-31 Thread Paul Cochrane via RT
On Tue Mar 27 12:08:14 2007, [EMAIL PROTECTED] wrote: On Saturday 24 March 2007 05:36, Klaas-Jan Stol wrote: attached a patch that adds a return statement to clone in iterator.pmc (which was obviously forgotten?) How interesting that it didn't fail on Linux with GCC. Anyway, applied