> The strict directive, is set to croak when an attempt to change the
> value of constant $str22 is made. Use of
>
> use strict(constdie);
Overall the proposal looks good. However, I think this should just be
"use strict 'constants'". This makes it consistent:
use strict qw(vars subs
On Tue, Aug 15, 2000 at 09:05:46AM +1000, Jeremy Howard wrote:
[much above that I agree with]
> And then of course there's character
> set type attributes (eg 'utf8')... These are not constraints, but they all
> use the same notation.
Aye. Acatualy, :utf8 and such aren't attributes proper, but in
As documented in RFC89, the format of declaration is
my $varname;
my (var-list);
my cast-type $varname;
my cast-type (var-list);
my $varname:constraint;
my (var-list):constraint;
my cast-type $varname:constraint;
my cast-type (var-l
8/14/2000 07:07:00 PM
To: Syloke Soong/Americas/NSC@NSC
cc: [EMAIL PROTECTED]@Internet
Subject: Re: RFC 89 (v2) Controllable Data Typing
I don't think this RFC is the place to try and cover all of the
'constraints' that might be in perl 6. Sure, this RFC may as we
> =head1 TITLE
>
> Controllable Data Typing
>
> =head1 VERSION
>
> Maintainer: Syloke Soong <[EMAIL PROTECTED]>
> Mailing List: [EMAIL PROTECTED]
>
<...>
>
> Retain current flexibility of Perl liberal variables.
> Provide a new form of declaring variables:
>
> scope cast-type $varname:constrai
mailto:[EMAIL PROTECTED]]
Sent: Monday, August 14, 2000 2:15 PM
To: Lipscomb, Al
Cc: '[EMAIL PROTECTED]'
Subject: Re: RFC 89 (v2) Controllable Data Typing
> Having methods and properties on the basic data types seems like a nice
> thing.
>
> Just a thought.
Check out RFC'
At 11:15 AM 8/14/00 -0700, Nathan Wiger wrote:
>I'm going to actually ask for a new mailing sublist, probably called
>-object, on which this should be discussed. There's lots and lots and
>lots and lots of details to work out.
It might be best to wait a bit and see how the proposed internal
repr
> Having methods and properties on the basic data types seems like a nice
> thing.
>
> Just a thought.
Check out RFC's 49 and 73. I've got an upcoming RFC that fleshes out the
idea that "All scalars should be objects in disguise".
I think this would be a really cool idea, and it is being discus
On Mon, Aug 14, 2000 at 01:46:55PM -0400, Lipscomb, Al wrote:
> While the implicit change works on most (if not all) situations it would be
> nice to have a way to control the conversion.
Sounds like an RFC to me :-)
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
lto:[EMAIL PROTECTED]]
Sent: Monday, August 14, 2000 1:40 PM
To: Lipscomb, Al
Cc: '[EMAIL PROTECTED]'
Subject: Re: RFC 89 (v2) Controllable Data Typing
On Mon, Aug 14, 2000 at 01:27:11PM -0400, Lipscomb, Al wrote:
> With some of the other suggestions to improve the "object" m
On Mon, Aug 14, 2000 at 01:27:11PM -0400, Lipscomb, Al wrote:
> With some of the other suggestions to improve the "object" model in Perl I
> was wondering if this would not be the time to ask about object-like
> behavior around the simple scalar things.
>
> For example if we had something like t
With some of the other suggestions to improve the "object" model in Perl I
was wondering if this would not be the time to ask about object-like
behavior around the simple scalar things.
For example if we had something like this:
my $id;
$id = "007";
print "My ID is $id->string\n";
Having meth
12 matches
Mail list logo
