Re: [perl #42170] [PATCH] Report line numbers on trailing_space.t

On 30/03/07, Eric Hanchrow <[EMAIL PROTECTED]> wrote: > "jerry" == jerry gay <[EMAIL PROTECTED]> writes: jerry> i've never run emacs, so i don't know the lispy analog. jerry> i'm sure somebody will chime in with it. This does what you think it does: (setq-default show-trailing-white

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

On 01/04/07, Allison Randal <[EMAIL PROTECTED]> wrote: 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

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

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, ap

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

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 ===

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

James, Failures in 'make test', reproduced via 'prove -v'. Please see attached. Unfortunately I'm not seeing any test failures with these files on linux x86 with r17914 (I believe yours is with r17912). I always get a bit jumpy when I've just done some commits and things start failing, so wo

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

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] r17913 - trunk/docs/pdds/draft

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:perl6-synopsis] r14367 - doc/trunk/design/syn

Author: larry Date: Sat Mar 31 18:59:24 2007 New Revision: 14367 Modified: doc/trunk/design/syn/S05.pod Log: quoting braino noticed by moritz++ Modified: doc/trunk/design/syn/S05.pod == --- doc/trunk/design/syn/S05.p

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

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 impor

Weekly Perl 6 mailing list summary for 4-10 March, 2007

Weekly Perl 6 mailing list summary This week on the Perl 6 mailing lists "Q: Can February March? A: No, but April May..." -- Larry Wall's r14313 log message for a date correction Language [svn:perl6-synopsis] r14308 - doc/trunk/design/syn David Green ask

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

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

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

# New Ticket Created by Ron Blaschke # Please include the string: [perl #42254] # in the subject line of all future correspondence about this issue. # 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. Test t/

Re: compilers/pirc continued...

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

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

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 n

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

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

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

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?)

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 s

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

[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 ne

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

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: Syntax for Constructing new Objects (and classes?)

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?)

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? It's implemented as a PCCMETHOD in the Class PMC, yes. Though at the moment you must write: $P2 = $P1.'new'() But that may well be a bug in I

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

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. getattribute

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

$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

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 shoul

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

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

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

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: Syntax for Constructing new Objects (and classes?)

Klaas-Jan Stol wrote: Hello, I have a short and simple question w.r.t. syntax for constructing new objects for the architect :-) Currently, it's done through: new P0, .Integer or in PIR: $P0 = new Integer # or .Integer I thought to have read somewhere this will be changed into something l

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

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

Re: [perl #42155] [PATCH] move members from Parrot_Interp to Parrot_Context

That's why I was surprised. Even if it doesn't improve performance (something it was never supposed to do in the first place), the question is whether it hurts performance significantly, e.g. whether the tradeoff between better code and faster code is worth it. Currently, I see no evidence that

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

Closing ticket.

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

Applied in r17899.

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

I decided to look further into this apparent error in Configure.pl: my @valid_opts = qw(ask bindir cage cc ccflags ccwarn cgoto cxx datadir #<-- line 292 ... sharedstatedir step sysconfdir verbose verbose-step=N version without-gdbm #<-- line 298 without-gmp without-icu yacc); I dec

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

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 cod

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

> "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 F to PATH. Ron> export PATH=/path/to/parrot/blib/lib:$PATH Ron> And then "make." OK, that gets me past that failu

Re: [perl #42229] PCCMETHOD Fails to Set Context in RetContinuation

chromatic (via RT) wrote: Invoking a RetContinuation requires freeing the current context (or at least decreasing its reference count). The problem is that the PCCMETHOD code doesn't set the current context in the RetContinuation PMC. Note that setting the current context is awfully ugly.

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

# New Ticket Created by Shawn M Moore # Please include the string: [perl #42236] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=42236 > Hi, I'm bored, so I'm going through and fixing some failing tests in t/codingstd/ At

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

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

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

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 o