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;# value
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 that. This is
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
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 thought as I have
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 beautiful
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.
That has been
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 Ctrue property is being set Ion the value in
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 means
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
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; #
* 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;
print
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
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 Ivalue in the
variable --
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
$a.true = 1
15 matches
Mail list logo
