On Thu, Sep 21, 2006 at 10:20:20PM -0700, Jonathan Lang wrote:
: Two questions:
:
: 1. How would the capture sigil affect the use of capture objects as
: replacements for perl5's references?
I don't see how it would have any effect at all, unless the P5 ref happened
to be to a typeglob, or had
Larry Wall wrote:
Jonathan Lang wrote:
: Two questions:
:
: 1. How would the capture sigil affect the use of capture objects as
: replacements for perl5's references?
I don't see how it would have any effect at all, unless the P5 ref happened
to be to a typeglob, or had both array and hash
On Fri, Sep 22, 2006 at 12:32:27AM -0700, Jonathan Lang wrote:
: Larry Wall wrote:
: Jonathan Lang wrote:
: : Two questions:
: :
: : 1. How would the capture sigil affect the use of capture objects as
: : replacements for perl5's references?
:
: I don't see how it would have any effect at all,
Larry Wall wrote:
: This would mean that the rules for capturing are as follows:
:
: * Capturing something in scalar context: If it is a pair, it is
: captured as a named argument; otherwise, it is captured as the
: invocant.
:
: * Capturing something in list context: Pairs are captured as named
Larry Wall wrote:
You don't need to use | to store a capture any more than you need @ to
store an array. Just as
$x = @b;
@$x;
gives you the original array,
Huh. I'm not used to this happening. So what would the following
code do, and why?
my @b = ('foo', 'bar');
my $x =
Randal L. Schwartz wrote:
A == A Pagaltzis [EMAIL PROTECTED] writes:
A * Randal L. Schwartz merlyn@stonehenge.com [2006-09-20 19:30]:
Fagyal == Fagyal Csongor [EMAIL PROTECTED] writes:
yet I never needed those HTML generating methods.
You've never made a
Am Donnerstag, 21. September 2006 22:40 schrieb Karl Forner:
Hello,
I've worked on the bug #40064, that was to test the shootout PIR programs
in examples/shootout.pir
Great. Thanks, applied as r14684.
- pidigits.pir do not work for the required value N=27. I suppose that's
because, as I
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40393]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40393
Hi,
This is a patch to hopefully finish off the emacs/vim C coda
additions, and
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40394]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40394
Hi,
This patch gets code_coda.t to test for multiply-defined codas (for
those
Jonathan Lang wrote:
Larry Wall wrote:
You don't need to use | to store a capture any more than you need @ to
store an array. Just as
$x = @b;
@$x;
gives you the original array,
Huh. I'm not used to this happening. So what would the following
code do, and why?
my @b = ('foo',
From S05:
If a subrule appears two (or more) times in any branch of a lexical
scope (i.e. twice within the same subpattern and alternation), or if the
subrule is quantified anywhere within a given scope, then its
corresponding hash entry is always assigned an array of
CMatch objects rather than
On Fri, Sep 22, 2006 at 10:22:52PM +0800, Audrey Tang wrote:
Moreover:
/foo bar bar foo+/
should set $foo to an Array with two Match elements, the first being a
simple match, and the second has multiple positional submatches.
The thinking behind the separate treatment is that in a
2006/9/22, Patrick R. Michaud [EMAIL PROTECTED]:
Out of curiosity, why not:
/foo bar bar $xyz:=(foo+)/
and then one can easily look at $xyz.from and $xyz.to, as well
as get to the arrayed elements? (There are other possibilities as
well.)
I'm not arguing in favor of or against the
Steffen Schwigon wrote:
snip
Thanks for reporting the solution back.
And it even works with unicode operators. Looks like we finally
really get our ankh, pentagram, and that smiley teddy bear from
that Grateful Dead album. (*) :-) Thanks to Unicode, thanks to Pugs
So hopefully in the same
On 9/22/06, Richard Hainsworth [EMAIL PROTECTED] wrote:
Biggest problems are the following:
a) finding the symbols - I had to use two editors, and getting them to
show them on screen
Good place to see all of the symbols in Unicode is
http://unicode.org/charts/symbols.html (a lot of PDF-files
On 9/21/06, via RT Paul Cochrane [EMAIL PROTECTED] wrote:
This patch gets code_coda.t to test for multiply-defined codas (for
those cases when a file append or automated tool adds a coda
unnecessarily). I have a feeling it's not pretty code, but my perl
foo is only slowly improving.
great
thanks, applied as r14688.
~jerry
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #40402]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40402
Hi,
http://svn.perl.org/viewcvs/parrot/trunk/src/ops/dotgnu.ops was meant
From: Paul Cochrane (via RT) [EMAIL PROTECTED]
Date: Thu, 21 Sep 2006 17:22:47 -0700
Hi,
. . .
I have a question about one file though: parrot/src/malloc-trace.c has
the following part in the coda that it currently has:
* compile-command:
*gcc -Wall -O -fpic
Am Freitag, 22. September 2006 19:22 schrieb Bernhard Schmalhofer:
Hi,
http://svn.perl.org/viewcvs/parrot/trunk/src/ops/dotgnu.ops was meant for
conversion ops for a C#-Implementation.
It looks obsolete to me, especially as there now is languages/dotnet.
Yep.
Does anybody mind, if I
Bernhard Schmalhofer (via RT) wrote:
http://svn.perl.org/viewcvs/parrot/trunk/src/ops/dotgnu.ops was meant for
conversion ops for a C#-Implementation.
It looks obsolete to me, especially as there now is languages/dotnet.
Does anybody mind, if I remove it?
I think remove it. I don't know
Aaron Sherman wrote:
IMHO most of the confusion here goes away if capture variables ONLY
store parameter-list-like captures, and any other kind of capture
should, IMHO, permute itself into such a structure if you try to store
it into one. That way, their use is carefully constrained to the
22 matches
Mail list logo
