Smylers schreef:
my $whatever
= do { my $baz = $bar * 17; my $quux = $baz - 3; $baz / $quux };
($bar better not be 3/17)
Just a rewrite:
my $whatever
= do { my $quux = (my $baz = $bar * 17) - 3; $baz / $quux };
And maybe even something like:
my $whatever
= do
On Mon, Nov 13, 2006 at 10:27:19PM -0800, chromatic wrote:
On Monday 13 November 2006 21:49, Patrick R. Michaud wrote:
On Mon, Nov 13, 2006 at 07:33:18PM -0800, [EMAIL PROTECTED] wrote:
Log:
Fix size mismatch errors, at least on Linux/PPC. If this breaks
other platforms, there's a
HaloO,
Smylers wrote:
BTW, could we define that the arithmetic shift ops do just that,
whereas the string ones do logical shift? And in addition that for
the bit inversion +^$a == -1 - $a holds? Note that -1 == +^0.
Does that assume a two's complement system? Is that a safe assumption
to
Author: pmichaud
Date: Tue Nov 14 09:07:04 2006
New Revision: 13477
Modified:
doc/trunk/design/syn/S04.pod
Log:
Correct punctuation.
Modified: doc/trunk/design/syn/S04.pod
==
--- doc/trunk/design/syn/S04.pod
Author: chip
Date: Tue Nov 14 09:40:26 2006
New Revision: 15527
Modified:
trunk/docs/pdds/pdd07_codingstd.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
Incremental improvement to pdd07 coding standards:
* Prefer char *p to char* p.
* Prefer
Hello everyone,
I was toying around with Pugs and I tried the following Perl 5 list assignment
my ($a, undef, $b) = 1..3;
Which gave me the following error message:
Internal error while running expression:
***
Unexpected ,
expecting word character, \\, :, * or parameter name
Am Dienstag, 14. November 2006 07:27 schrieb chromatic:
Does this patch do anything for you? I sort of really hate it, but I'm
curious about the results.
I've now ci'ed that, as it obviosly fixes x86_64 so far.
Thanks for invetigating it.
leo
I don't know if this was cc'ed to p2p, so just in case.
leo
---BeginMessage---
Leo,
We have PMCs in the pirate repo at the moment. They are based off of
the python pmcs in parrot's repo, but work with recent versions of
parrot. Not all features are enabled at the moment, but I haven't had
a lot
[ I'll post this to use.perl.org when CPAN has had a chance to mirror. ]
On behalf of the Parrot team, I'm proud to announce Parrot 0.4.7, Caique!
What is Parrot? Parrot is a virtual machine aimed at running all dynamic
languages. The Parrot project home page is parrotcode.org.
You may now
# New Ticket Created by Chip Salzenberg
# Please include the string: [perl #40884]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40884
All those cute release names seem to have been lost to history. Please
somebody
jerry gay wrote:
ick -- that feels wrong for parrot. we've always tried to make parrot
act in a consistent way across platforms wherever possible, so i'd
rather see the fix in Parrot_sprintf rather than in t/op/sprintf.t.
For the record: we decided in the weekly meeting yesterday to go with
Matt Diephouse wrote:
Would anyone be inconvenienced if the set_pmc vtable and the
setref and deref opcodes were removed? Note that if you are using set
_pmc but are not using assign_pmc, then you may not be
inconvenienced because right now the default assign_pmc vtable calls
set_pmc.
These
Patrick R. Michaud wrote:
Or, in claiming that compilers have an API, should we instead
say that the canonical compilation sequence is to use compreg
to obtain a compiler object (not an invokable sub), and then
compile the source via a 'compile' method on the compiler object?
For example:
On 11/9/06, Patrick R. Michaud [EMAIL PROTECTED] wrote:
Opinions welcome. Personally I think I favor the a compiler is
an object with a 'compile' method model, and that Ccompreg gives
us back a compiler object as opposed to a subroutine-like thing.
For the record, it was decided (Allison++)
On Tue, Nov 14, 2006 at 08:52:47PM -0800, Allison Randal wrote:
Also for the record from the weekly meeting (which was actually today,
just a very long today): Yes, compilers are objects and compilation is a
method call. The compiler for TGE tree grammars is implemented this way,
and it's
I just finished reviewing docs/dev/pmc_object_design_meeting_notes.pod,
which is a summary of a design discussion I asked particle to lead at
the hackathon last weekend. It's a fantastic piece of work, and nicely
organizes the ideas we've been kicking around the past few months.
Thanks to
On Tuesday 14 November 2006 22:28, Allison Randal wrote:
I've added responses after each recommendation, if you have any
questions or comments pull them onto the mailing list.
Properties:
I don't remember what problem these try to solve. It's difficult to
discuss
one way or the
17 matches
Mail list logo
