[S03] Negation metaoperator

Generalize the negated relational operators to apply to any infix operator that returns a boolean. In terms of the standard operators, this will add <&& || ^^ // and or xor err> to the family that is implicitly equipped with logical negations. For consistency's sake, you may also want to define

[S03] Range Semantics

Inspired by the new array indexing syntax from S09. Modify S03 (under "Range Semantics") so that if a Range is operating in a bounded space, a 'whatever' star as the starting or ending point maps to the lower or upper bound: my enum Months «:Jan(1) Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec»

[S03] typo

@@ -749,7 +749,7 @@ These operators compare their operands using numeric, string, or C semantics respectively, and depending on the order return one of C, C, or C -(which numerify to -1, 0, or +1). See L. +(which numerify to -1, 0, or +1). See L. =item *

Re: Use of English pragma

Leopold Toetsch wrote: Am Donnerstag, 5. April 2007 07:35 schrieb jerry gay: developers shouldn't live in fear of $^O And the docs for some such are not far away: $ perldoc perlvar /\$\^O Okay, then I'll convert to regular variable in Configure.pl in the course of refactoring. And then

Re: [perl #42313] improper casting to void * in src/dynext.c

Am Donnerstag, 5. April 2007 17:22 schrieb via RT: > # New Ticket Created by > # Please include the string: [perl #42313] > # in the subject line of all future correspondence about this issue. > # http://rt.perl.org/rt3/Ticket/Display.html?id=42313 > > > > load_func is not a void pointer. > > Inde

Re: Use of English pragma

Am Donnerstag, 5. April 2007 07:35 schrieb jerry gay: > developers shouldn't live in fear of $^O And the docs for some such are not far away: $ perldoc perlvar /\$\^O leo - yes, typing this needs escaping, but you knew that already - it's Perl ;)

Re: [svn ci] NCI methods now name-mangled

Am Donnerstag, 5. April 2007 00:39 schrieb Jonathan Worthington: > Don't really need a policy to tell me that breaking stuff for languages > folks sucks. :-) I try hard to avoid it, but unfortunately stuff slips > through the net occasionally. In this case, I wasn't even aware that you > could use

[perl #41860] [CAGE] Run Parrot under Coverity Prevent

On Thu Mar 15 19:24:31 2007, ptc wrote: > Coverity already runs Prevent on the Perl 5 source. Let's get > Parrot running under it, too. L Just to keep this ticket up to date with what's happening, here is a reply to my email asking to add Parrot to Coverity which recen

[perl #42312] src/pmc/os.pmc: bad use of stat(2) and lstat(2)

# New Ticket Created by # Please include the string: [perl #42312] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=42312 > in src/pmc/os.pmc after retrieving the information of a file with stat or lstat all the fields are s

Re: [svn ci] PMC documentation guidelines draft

Joshua Isom wrote: On Apr 5, 2007, at 10:45 AM, Klaas-Jan Stol wrote: jerry gay wrote: i've recently committed (r17998) a draft of PMC documentation guidelines, for your review. This document is meant to formalize, clarify, and extend the current de facto style for documentation of core PMCs.

[perl #42313] improper casting to void * in src/dynext.c

# New Ticket Created by # Please include the string: [perl #42313] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=42313 > load_func is not a void pointer. Index: src/dynext.c ==

Re: [svn ci] PMC documentation guidelines draft

On Apr 5, 2007, at 10:45 AM, Klaas-Jan Stol wrote: jerry gay wrote: i've recently committed (r17998) a draft of PMC documentation guidelines, for your review. This document is meant to formalize, clarify, and extend the current de facto style for documentation of core PMCs. you'll find the docu

Re: [svn ci] PMC documentation guidelines draft

jerry gay wrote: i've recently committed (r17998) a draft of PMC documentation guidelines, for your review. This document is meant to formalize, clarify, and extend the current de facto style for documentation of core PMCs. you'll find the document at docs/pmc/documentation.pod. highlights: ~ br

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

On 4/4/07, Allison Randal <[EMAIL PROTECTED]> wrote: Alek Storm wrote: > > Whoops, that metaclasses reference didn't quite make sense (it was pretty > late in my timezone). I meant that, in Smalltalk for example, classes are > also first-class objects. Also, in prototype-based languages like

[svn ci] PMC documentation guidelines draft

i've recently committed (r17998) a draft of PMC documentation guidelines, for your review. This document is meant to formalize, clarify, and extend the current de facto style for documentation of core PMCs. you'll find the document at docs/pmc/documentation.pod. highlights: ~ brings many things w