As far as I understood, arrays and hashes, and references them are much
more similar in Perl6 than it was in Perl5.
F.e. we have @a and $a = [EMAIL PROTECTED];
the same:
push @a,1,2,3 push $a, 1,2,3
$b = @a $b = $a
(?) say "@a[]" say "$a[]"
(?) myfunc( [EMAIL PROTECTED
On Thu, 25 Nov 2004 13:45:51 -0800, Larry Wall <[EMAIL PROTECTED]> wrote:
...
Hmm, I would say that "" is short for qq//, not qq"". Quote characters
lose their identity when used with generalized quotes. (I realize this
is not always true with Perl 5, but that can be construed as a mistake.)
So Â
On Thu, Nov 25, 2004 at 09:37:21PM +0100, Juerd wrote:
: Larry Wall skribis 2004-11-25 9:39 (-0800):
: > : How is <<'END' disambiguated from <<'qw' list>>, anyway?
: > To get the qw// parse you must put a space between the << and the
: > quote. This is no hardship semantically, since qw// has alw
Larry Wall writes:
> PerlMonks has no problem displaying «», but I haven't a clue how to
> type it into my browser yet.
If your browser is using Gnome then holding down Ctrl+Shift while typing
AB (for «) or BB (for ») might work. (This is also working for me
typing this in 'Vim' in a 'Gnome Term
On Thu, Nov 25, 2004 at 11:12:32PM +0100, Juerd wrote:
: But if mixed «>> is allowed, isn't that «<<»syntax error? Or did I
: misinterpret the answer re mixing them?
Uh, I wasn't aware that I'd actually answered the question. :-)
My actual inclination is to disallow it. I was just trying to arg
Larry Wall skribis 2004-11-25 13:45 (-0800):
> Hmm, I would say that "" is short for qq//, not qq"". Quote characters
> lose their identity when used with generalized quotes. (I realize this
> is not always true with Perl 5, but that can be construed as a mistake.)
> So «» is not really short for
Adam Kennedy writes:
> Herbert Snorrason wrote:
> >On Thu, 25 Nov 2004 22:00:03 +1100, Adam Kennedy <[EMAIL PROTECTED]> wrote:
> >
> >>And just after the snip you will see I qualify "parse" in this context
> >>as loading the perl in some form of DOM-type tree.
> >
> >And yet you disqualify the Perl
On Thu, Nov 25, 2004 at 09:55:54PM +0100, Juerd wrote:
: As we now know, in many situations, << and « mean the same thing. In
: exactly those situations, the same is true for >> and ». However,
: sometimes, « cannot be used where << can. Here-docs are an example.
:
: «» (or <<>>, if you wish) quot
Juerd writes:
> As we now know, in many situations, << and « mean the same thing. In
> exactly those situations, the same is true for >> and ». However,
> sometimes, « cannot be used where << can. Here-docs are an example.
Why can't « be used for here-docs? I thought Larry had said they were
com
As we now know, in many situations, << and « mean the same thing. In
exactly those situations, the same is true for >> and ». However,
sometimes, « cannot be used where << can. Here-docs are an example.
«» (or <<>>, if you wish) quotes. I am assuming that «» is a shorthand
for qw«», except where s
Larry Wall skribis 2004-11-25 9:39 (-0800):
> : How is <<'END' disambiguated from <<'qw' list>>, anyway?
> To get the qw// parse you must put a space between the << and the
> quote. This is no hardship semantically, since qw// has always thrown
> away initial and trailing whitespace.
> Under one
Adam Kennedy wrote:
What I'm after are 3 critical features.
1. You always get back out what you put in.
$source eq serialize(parse($source)).
As Larry pointed out, this will depend on how much metadata your parser
augments your parse-tree with. I think it will be doable (probably by
subclassing t
Herbert Snorrason wrote:
On Thu, 25 Nov 2004 22:00:03 +1100, Adam Kennedy <[EMAIL PROTECTED]> wrote:
And just after the snip you will see I qualify "parse" in this context
as loading the perl in some form of DOM-type tree.
And yet you disqualify the Perl6 rule system, with its tree of match
objects
On Thu, Nov 25, 2004 at 11:59:21AM -0600, Rod Adams wrote:
: Seeing the « in the context of a here-doc made me think "can you do a
: »<< here-doc?"
Nope, you can only hyper operators, not terms.
: So, something like :
:
: @text = »<
On Thu, Nov 25, 2004 at 02:31:46PM +1100, Adam Kennedy wrote:
: >Let's say you want to write a yacc grammar to parse Perl 6, or
: >Parse::RecDescent, or whatever you're going to use. Yes, that will be
: >hard in Perl 6. Certainly harder than it was in Perl 5.
:
: In the end, I concluded there wa
Juerd wrote:
Thomas Seiler skribis 2004-11-25 14:52 (+0100):
Is $heredoc = «END; the same as $heredoc = <
I certainly hope not.
Quoting the delimiter is needed, by the way.
How is <<'END' disambiguated from <<'qw' list>>, anyway?
Seeing the « in the context of a here-doc made me think "c
On Thu, Nov 25, 2004 at 05:03:36PM +0100, Juerd wrote:
: Thomas Seiler skribis 2004-11-25 14:52 (+0100):
: > Is $heredoc = «END; the same as $heredoc = <>, anyway?
To get the qw// parse you must put a space between the << and the
quote. This is no hardship semantically, since qw// has always thro
Dave Whipp wrote:
gather @bin1, @bin2 -> $bin1, $bin2{
for @words {
$bin1.take if /^^a/;
$bin2.take if /e$$/;
}
}
Juerd point out (private email) that my example doesn't really make any
sense in that it doesn't do anything over and above s/take/push.
However, I think the concept of mul
Thomas Seiler skribis 2004-11-25 14:52 (+0100):
> Is $heredoc = «END; the same as $heredoc = <>, anyway?
Regards,
Juerd
Hi
Is $heredoc = «END; the same as $heredoc = <
thomas
On Thu, 25 Nov 2004 22:00:03 +1100, Adam Kennedy <[EMAIL PROTECTED]> wrote:
> And just after the snip you will see I qualify "parse" in this context
> as loading the perl in some form of DOM-type tree.
And yet you disqualify the Perl6 rule system, with its tree of match
objects? What, exactly, is i
Smylers wrote:
Adam Kennedy writes:
perl itself would also appear unable to understand perl source,
instead doing what I would call RIBRIB parsing, "Read a bit, run a
bit".
RIBRIB? RABRAB, surely!
Smylers
Yes, you are right, typo.
Michele Dondi wrote:
On Thu, 25 Nov 2004, Adam Kennedy wrote:
I thought it was about time I brought some concerns I've been having
lately to the list. Not so much on any particular problem with perl6,
but on problems with perl5 we would seem to have the opportunity to
fix but aren't. (So far as
Let's say you want to write a yacc grammar to parse Perl 6, or
Parse::RecDescent, or whatever you're going to use. Yes, that will be
hard in Perl 6. Certainly harder than it was in Perl 5.
In the end, I concluded there was _no_ way to write even a Perl 5 parser
using any sort of pre-rolled gramm
On Wed, 24 Nov 2004, Dave Whipp wrote:
Juerd point out (private email) that my example doesn't really make any
sense in that it doesn't do anything over and above s/take/push.
However, I think the concept of multiple bins could still be useful. My
What about an adverb? Hope not to say anything utte
On Thu, 25 Nov 2004, Adam Kennedy wrote:
I thought it was about time I brought some concerns I've been having lately
to the list. Not so much on any particular problem with perl6, but on
problems with perl5 we would seem to have the opportunity to fix but aren't.
(So far as I can tell).
So why n
On Wed, 24 Nov 2004, David Ross wrote:
I have been studying PERL 5 core and modules to identify options and
issues for meta-architectures and automated code generation. PERL 6
documents and discussion provide insight essential to effectively using
PERL 5 and preparing for PERL 6.
[snip]
developing
27 matches
Mail list logo
