Damian Conway skribis 2006-08-31 9:08 (+1000):
> return want.rw ?? $lvalue
> :: want.count == 2 ?? (7,11)
> :: want.item ?? 42
> :: want.list ?? 1..10
> ::die "Bad context;
s:g/::/!!/ # :)
Juerd
--
http://convolution.
Rather, the proposal is focusing on what users of these data structures
would / could see. The idea is that relational structures have the same
ease of use and flexability that things like hashes or arrays or sequences
or sets do now. They can of course just be stored in RAM like the
aforemen
On Wednesday 30 August 2006 19:14, Luke Palmer wrote:
> The problem with PHP is not that it has
> too much functionality, but that it is organized extremely poorly.
That's really my point. I'm all for adding necessary features to Parrot where
they're appropriate, but not in such a way that they
What compiler is generating warnings?
-J
--
On Tue, Aug 29, 2006 at 07:03:44PM -0700, Will Coleda wrote:
> # New Ticket Created by Will Coleda
> # Please include the string: [perl #40253]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/
According to S05, the string method equivalent of the s/// operator is named
"subst". (Just going by the spec here; the method doesn't exist yet in
Pugs). I anticipate typos galore from the near-collision of names between
"subst" and "substr"; perhaps "replace" would be a better name, even thoug
Mark J. Reed skribis 2006-08-31 9:45 (-0400):
> According to S05, the string method equivalent of the s/// operator is named
> "subst". (Just going by the spec here; the method doesn't exist yet in
> Pugs). I anticipate typos galore from the near-collision of names between
> "subst" and "substr"
On 8/31/06, Juerd <[EMAIL PROTECTED]> wrote:
Another issue is how we're going to pass arguments to this method. s///
has very special syntax, that I don't think we can easily replicate.
S05 says it's $str.subst(regex, string-or-block); presumably the flags would
go on the regex?
I personally
On 8/31/06, Mark J. Reed <[EMAIL PROTECTED]> wrote:
I anticipate typos galore from the near-collision of names between
"subst" and "substr"; perhaps "replace" would be a better name, even
though
it breaks the mnemonic association with s///?
Perhaps the long name "substitute" would work? While
Mark J. Reed skribis 2006-08-31 10:29 (-0400):
> >Another issue is how we're going to pass arguments to this method. s///
> >has very special syntax, that I don't think we can easily replicate.
> S05 says it's $str.subst(regex, string-or-block); presumably the flags would
> go on the regex?
Ah, bl
gcc 4.0.1, os x 10.4.7, PPC, ccflags .= " -pipe -fno-common -Wno-long-
double -Wno-long-long -std=c89 -pedantic ";
(which is still too many warnings, but leo noted this particular one
could stand to be fixed, as time permits.)
On Aug 31, 2006, at 5:34 AM, Joshua Hoblitt wrote:
What compile
* Ryan, Martin G <[EMAIL PROTECTED]> [2006-08-31 03:30]:
> "This is a similar problem that Forth and Lisp had."
>
> How so? Are they multi-paradigmatic leading to a large and
> rich selection of syntax and approaches to choose from? Or do
> they try to shoe-horn you into a specific approach that
On 8/31/06, Juerd <[EMAIL PROTECTED]> wrote:
Still, though, How would you specify :g? It doesn't make a lot of sense
on rx// -- just like you can't use it with qr// in Perl 5.
It is a good point that it doesn't belong on the regex. Perhaps:
$foo.subst(/bar/, "baz", :g)
That seems to work,
On 8/31/06, Luke Palmer <[EMAIL PROTECTED]> wrote:
On 8/31/06, Juerd <[EMAIL PROTECTED]> wrote:
> Still, though, How would you specify :g? It doesn't make a lot of sense
> on rx// -- just like you can't use it with qr// in Perl 5.
It is a good point that it doesn't belong on the regex. Perhaps:
> $foo.subst(:g, /bar/, "baz")
>
i seem to recall
$foo.subst(/:g bar/, "baz")
is valid syntax already.
If I'm not mistaken, the aversion to that syntax- as implied earlier in this
thread- was that the :g is really a modifier on the substitution, not on the
matching. (Please correct
Luke Palmer wrote:
On 8/31/06, Juerd <[EMAIL PROTECTED]> wrote:
> Still, though, How would you specify :g? It doesn't make a lot of sense
> on rx// -- just like you can't use it with qr// in Perl 5.
It is a good point that it doesn't belong on the regex. Perhaps:
$foo.subst(/bar/, "baz", :
> From: A. Pagaltzis [mailto:[EMAIL PROTECTED]
>
> * Ryan, Martin G <[EMAIL PROTECTED]> [2006-08-31 03:30]:
> > In certain problem domains each remains the language of choice.
> > They weren't aiming to solve as broad a range of problems as
> > perl does so one shouldn't expect them to have as hi
16 matches
Mail list logo
