On Sun, May 20, 2001 at 01:24:29PM +0100, Simon Cozens wrote:
> On Sun, May 20, 2001 at 12:46:35AM -0500, Jonathan Scott Duff wrote:
> > my $a is true = 0; # variable property
> > my $a = 0 is true; # variable property
> > my ($a) = 0 is true;# val
On Sun, May 20, 2001 at 06:19:35PM -0400, Uri Guttman wrote:
> > "DC" == Damian Conway <[EMAIL PROTECTED]> writes:
>
>
> DC> return undef Because($borked);
>
> hmm, that is poor code as returning a real undef will break in a list
> context.
I always balk when I see someone say th
On Mon, May 21, 2001 at 08:57:45AM +0100, Graham Barr wrote:
> So far all I can think of for variable properties are actually compile time
> properties like constant etc.
> So I am left wondering how much of an issue this really will be ?
The beautiful and the horrible thing about Perl is that th
Graham wrote:
> > >my $a is true = 0; # variable property
> > >my $a = 0 is true; # variable property
> > >my ($a) = 0 is true;# value property
> >
> > Wow. Totally ETOOCONFUSING.
>
> That has been exactly my thou
Peter wrote:
> >$ref =
> > sub{my%k;@k{@{+pop}}=\(@_);splice@_,$_,!$k{$_}for reverse
> > 0..@_;\@_}->(@A,\@I);
>
> Oh, well, if I'd known it was *that* succinct...
>
> But... that *does* involve copying; the original poster was talking
> about huge arrays where copyin
Simon Cozens <[EMAIL PROTECTED]> writes:
> On Mon, May 21, 2001 at 08:57:45AM +0100, Graham Barr wrote:
> > So far all I can think of for variable properties are actually compile time
> > properties like constant etc.
> > So I am left wondering how much of an issue this really will be ?
>
> The
Damian Conway <[EMAIL PROTECTED]> wrote
>> > >my $a is true = 0; # variable property
>> > >my $a = 0 is true; # variable property
>> > >my ($a) = 0 is true;# value property
>> >
>> > Wow. Totally ETOOCONFUSING.
>
1) It looks like properties proposed will introduce an inconsistency in
naming conventions. In OO-Perl programmers are advised to use leading
lowercase for object methods and leading uppercase for class methods.
Properties are lowercase for built-ins and uppercase for user-defined. Don't
we need t
On Mon, May 21, 2001 at 08:57:45AM +0100, Graham Barr wrote:
> On Sun, May 20, 2001 at 01:24:29PM +0100, Simon Cozens wrote:
> > On Sun, May 20, 2001 at 12:46:35AM -0500, Jonathan Scott Duff wrote:
> > > my $a is true = 0; # variable property
> > > my $a = 0 is true;
On Mon, May 21, 2001 at 10:01:28AM -0700, Dave Storrs wrote:
> First of all, thanks for putting this table together; this is good way to
> clear all the up.
You're welcome.
> Could we revist the idea of alternate syntax to disambiguate between
> value and variable cases? Perhaps now that we've f
* Jonathan Scott Duff <[EMAIL PROTECTED]> [05/21/2001 09:39]:
>
> If anything, all variables should have a "value" property that evaluates
> to its, well, value and only that property would be considered in
> conditionals. Then these would be equivalent:
>
> print keys (+$foo).prop;
>
On Mon, May 21, 2001 at 12:47:15PM -0700, Dave Storrs wrote:
> On Mon, 21 May 2001, Jonathan Scott Duff wrote:
> > Would you also advocate separate declarative syntax for variable
> > properties and value properties? That's where I think much confusion
> > will be.
>
> Yes, I would. What
Dave Storrs wrote:
> Second: I'm afraid that even after all this discussion and puzzling over
> this table for a bit, I'm still a bit baffled by this stuff. Perhaps I'm
> just slow, but let's assume for the sake of argument that I'm not the only
> one still scratching his head. C
Scott wrote:
> Would you also advocate separate declarative syntax for variable
> properties and value properties? That's where I think much confusion
> will be.
That's covered in my new proposal too.
Damian
On Mon, 21 May 2001, Jonathan Scott Duff wrote:
> On Mon, May 21, 2001 at 10:01:28AM -0700, Dave Storrs wrote:
>
> Would you also advocate separate declarative syntax for variable
> properties and value properties? That's where I think much confusion
> will be.
Yes, I would. What th
On Mon, May 21, 2001 at 08:04:58AM -0500, Jarkko Hietaniemi wrote:
> All this talk about slices reminds me of this:
>
> http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2000-10/msg00024.html
>
> Although in this thread the idea was more in the way of an internal
> implementation (e.g. to
On Sat, May 19, 2001 at 11:30:40AM +1000, Damian Conway wrote:
> I obviously didn't do an adequate job the first time.
I don't know about that, but the universe of Perl 6 properties is
looking clearer to me now and I thank you for it.
> Here, the C property is being set I in $result and that
> a
On Mon, 21 May 2001, Jonathan Scott Duff wrote:
> So, if I have a Dog $spot, here's a little table where a 1 in the M
> column means $spot has a bark method that says 'woof', 1 in the V column
> means $spot has a bark variable (compile-time) property that says 'arf'
> and a 1 in the A column me
Scott Duff wrote:
> > $bar is Open;
> > $bar is Open("from 5pm");
> > $bar{soom} is Open("from 5pm");
> > "bar" is Open("from 5pm");
> > 1 is Open("from 5pm");
> >
> > Note that in the first three of the above cases, it's the I > vari
This is, obviously, premature, but, since the list has been rather
inactive over the last week or so (and this stuff has been much on
my mind as of late), I thought I'd throw this out there, fwiw.
I'm probably all wet ("And that's, OK" :-), but, recently, I began
to re-review my copy of Jon Meyer
Ok, the idea of a master-apprentice program, where the wannabes,
while working with masters, sort-of cut their teeth on the docs, and
then move up in skills over time, has been mentioned a few times on
this list and discussed rather extensively on perl6-meta. Now, I'm
wondering, has a consensus o
Not to speak for Dan, but there's no code yet to review or learn from.
I'd love to see someone set up a perl *5* apprentice program, and
Mark-Jason Dominus has some ideas on how it might work. For perl6,
though, we're not yet at a place where I think it makes sense. Right
now there's so little d
On Mon, May 21, 2001 at 05:43:28PM -0600, Nathan Torkington wrote:
> Not to speak for Dan, but there's no code yet to review or learn from.
> I'd love to see someone set up a perl *5* apprentice program, and
> Mark-Jason Dominus has some ideas on how it might work. For perl6,
> though, we're not
> Err. There are only two things: compile-time variable properties and
> run-time value properties. Attributes are a Perl 5 construct that we're
> renaming because the name conflicts with the OO term for object data.
So,
$a is true
and
$a.true = 1
are synonyms, right?
if not, then there are
> > Err. There are only two things: compile-time variable properties and
> > run-time value properties. Attributes are a Perl 5 construct that we're
> > renaming because the name conflicts with the OO term for object data.
>
> So,
>
> $a is true
>
> and
>
> $
25 matches
Mail list logo
