HaloO,
Jonathan Lang wrote:
I agree that the distinctions between the five different equality
tests (=:=, ===, eqv, ==, eq) are rather difficult to grasp (I'm still
having trouble getting the difference between '===' and 'eqv', and
would appreciate some help).
So let's try to join our half kno
You guys should read The Search for the Perfect Language, by Umberto Eco.
It would disabuse you of the notion that perfect orthogonality is possible
or even desirable.
Larry
On Tue, Nov 14, 2006 at 10:15:42PM -0500, Vincent Foley wrote:
: 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:
:
On 11/14/06, Vincent Foley <[EMAIL PROTECTED]> wrote:
I was toying around with Pugs and I tried the following Perl 5 list assignment
my ($a, undef, $b) = 1..3;
Huh. I didn't think that worked in Perl 5, either. What am I misremembering?
I distinctly recall having to do things like (my $a,
Author: larry
Date: Wed Nov 15 09:35:04 2006
New Revision: 13478
Modified:
doc/trunk/design/syn/S02.pod
Log:
Clarifications on use of identifiers, names, and bare sigils.
Modified: doc/trunk/design/syn/S02.pod
==
---
On 11/15/06, Mark J. Reed <[EMAIL PROTECTED]> wrote:
On 11/14/06, Vincent Foley <[EMAIL PROTECTED]> wrote:
> I was toying around with Pugs and I tried the following Perl 5 list assignment
>
> my ($a, undef, $b) = 1..3;
Huh. I didn't think that worked in Perl 5, either. What am I misrememberi
> > my ($a, undef, $b) = 1..3;
>
> Huh. I didn't think that worked in Perl 5, either. What am I
> misremembering? I distinctly recall having to do things like (my $a, undef,
> my $b) to avoid errors because you can't assign to undef. Maybe I'm just
> hallucinating.
Are you remembering this:
Hi all,
The attached patch to the coding standards pdd concerns how we handle
the parrot emacs/vim coda in perl source files when the files contain
__END__ or __DATA__ blocks. The reason for the patch is that vim looks
at only the first or last five lines of a file to see if there is any
styl
On Nov 15, 2006, at 12:04 PM, Mark J. Reed wrote:
On 11/14/06, Vincent Foley <[EMAIL PROTECTED]> wrote:
I was toying around with Pugs and I tried the following Perl 5
list assignment
my ($a, undef, $b) = 1..3;
Huh. I didn't think that worked in Perl 5, either. What am I
misrememberi
Author: larry
Date: Wed Nov 15 10:44:13 2006
New Revision: 13479
Modified:
doc/trunk/design/syn/S02.pod
Log:
Clarification of $::foo et al. suggested by [partical]++
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/
Patrick R. Michaud wrote:
We might want to resurrect the 'compile' opcode as an indirect syntax
for making the 'compile' method call.
Maybe, but I can't see that this is worthy of a special opcode
(and presumably a vtable slot?). There's just not a lot of
difference between:
$P0 = compi
Am Mittwoch, 15. November 2006 05:52 schrieb Allison Randal:
> We might want to resurrect the 'compile' opcode as an indirect syntax
> for making the 'compile' method call.
Please don't. Opcodes are very limited re calling conventions. Mehthods are by
far more flexible when it comes to pass argum
Leopold Toetsch wrote:
Please don't. Opcodes are very limited re calling conventions. Mehthods are by
far more flexible when it comes to pass arguments to compilers.
I believe we've been through this conversation before. I don't mean
coding a completely different opcode, I just mean using th
Hi @all,
[ shortened: ]
Recommendation: Deprecate property support in PMCs.
Allison: Would it help if we call them "static attributes" and "dynamic
attributes"?
No. Attributes and properties are almost orthogonal concepts.
Properties are per PMC (or object, as that's a PMC too)
Am Mittwoch, 15. November 2006 22:38 schrieb Allison Randal:
> Leopold Toetsch wrote:
> > Please don't. Opcodes are very limited re calling conventions. Mehthods
> > are by far more flexible when it comes to pass arguments to compilers.
>
> I believe we've been through this conversation before. I d
On Wed, Nov 15, 2006 at 05:41:24PM +, Ævar Arnfjörð Bjarmason wrote:
> On 11/15/06, Mark J. Reed <[EMAIL PROTECTED]> wrote:
> >On 11/14/06, Vincent Foley <[EMAIL PROTECTED]> wrote:
> >> I was toying around with Pugs and I tried the following Perl 5 list
> >assignment
> >>
> >> my ($a, undef,
On Wed, Nov 15, 2006 at 11:17:57PM +, Nicholas Clark wrote:
> I thought that allowing undef in my ($a, undef, $b) came in around 5.004ish,
> but I can't find it in perldelta, and I don't have a version compiled to
> test with (or any quick way to compile them, given that pretty much only
> AIX
Leopold Toetsch wrote:
>
> Properties are never inherited, they belong to just that one PMC.
Well, yeah. That's what they're designed to do. But agreed that for the
sake of clarity attributes and properties should keep two separate names.
> Therefore a
> much more efficient implementation of c
chromatic wrote:
Properties:
I don't remember what problem these try to solve. It's difficult to discuss
one way or the other without an example.
They're solving the problem of allowing attribute-like information to be
attached to an object at runtime. In Perl 5, objects are blessed hashes
On Wednesday 15 November 2006 17:04, Allison Randal wrote:
> Will this not be alleviated by the new variable-sized PMCs you're
> prototyping? Anyway, I can't see that allocating storage for a single
> reference to another data structure is going to break the bank.
Seems like you'd always pay for
On 11/15/06, Ævar Arnfjörð Bjarmason <[EMAIL PROTECTED]> wrote:
On 11/15/06, Mark J. Reed <[EMAIL PROTECTED]> wrote:
> On 11/14/06, Vincent Foley <[EMAIL PROTECTED]> wrote:
> > I was toying around with Pugs and I tried the following Perl 5 list
assignment
> >
> > my ($a, undef, $b) = 1..3;
>
>
Leopold Toetsch wrote:
And, I do think making the PASM and PIR compilers capable of being used
as standard compiler objects is a superior solution.
We currently can't pass any arguments to PASM/PIR compilers. You can't change
trace or debug options for "eval". This is a serious limitation, w
On 11/15/06, Dave Mitchell <[EMAIL PROTECTED]> wrote:
$ perl-5322 -we'my ($x,undef,$y) = 1..3'
Can't declare undef operator in my at -e line 1, near ") ="
Execution of -e aborted due to compilation errors.
$ perl545 -we'my ($x,undef,$y) = 1..3'
$
Ah-hah! So I'm not crazy! Necessarily, anyway.
23 matches
Mail list logo
