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 Fri 26 Nov 2004 06:15, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 26, 2004 at 03:57:43PM +1100, Andrew Savige wrote:
> > To try and cheer you up a bit, I'm delighted to report that your new
> > Test-Simple-0.51 passed all tests on Windows XP under Perl 5.8.5
> > using NMAKE.
>
>
On Fri, Nov 26, 2004 at 03:57:43PM +1100, Andrew Savige wrote:
> To try and cheer you up a bit, I'm delighted to report that your new
> Test-Simple-0.51 passed all tests on Windows XP under Perl 5.8.5
> using NMAKE.
Thank you, I am very much lacking in Windows tuits at the moment.
--
Michael G
--- Michael G Schwern wrote:
> Excuse me for a moment.
>
> I AM SO SICK OF THREADING BUGS!!! BLARHGAGHAGHAHGAH! I don't even USE
> THREADS and I seem to find all the bugs!! ARGH!!!
>
> *ahem*
To try and cheer you up a bit, I'm delighted to report that your new
Test-Simple-0.51 passed all tes
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:17:38PM -0600, Danny R. Faught wrote:
> $ /usr/bin/perl.exe "-MExtUtils::Command::MM" t/threads.t
> 1..6
> ok 1 - Each of these should app the test number
> Segmentation fault (core dumped)
>
> $ perl -v
>
> This is perl, v5.8.5 built for cygwin-thread-multi-64int
Excu
I tried it on Windows XP Pro on three different configurations - Cygwin
perl, ActiveState 5.8.4 and ActiveState 5.6.1. The first had a test
failre, and the other two failed to build.
$ make test
/usr/bin/perl.exe "-MExtUtils::Command::MM" "-e" "test_harness(0,
'blib/lib', 'b
lib/arch')" t/*.t
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
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
Okay, I'm confused, I thought that the whole point of a caller saves,
continuation passing regime was that the caller only saves what it's
interested in using after the function returns. Exactly *where* that
return happens, and whether it happens more than once, is completely
irrelevant from the po
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
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 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
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Tuesday 23 November 2004 23:44, Michael G Schwern wrote:
> On Tue, Nov 23, 2004 at 10:51:26PM +0100, Tels wrote:
> > On Tuesday 23 November 2004 10:57, Michael G Schwern wrote:
> > > http://www.pobox.com/~schwern/Test-Simple-0.51.tar.gz
> >
> > Just wan
Thomas Seiler skribis 2004-11-25 14:52 (+0100):
> Is $heredoc = «END; the same as $heredoc = <>, anyway?
Regards,
Juerd
Transcendental (and some other) ops that have a FLOATVAL out argument
and INTVAL source argument(s) are deprecated.
E.g.
acos Nx, Iy
atan Nx, Iy, Iz
Actually these opcodes aren't emitted any more, you'll get
set $N0, Iy
acos Nx, $N0
for registers or a floatval constant for constants.
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 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
26 matches
Mail list logo
