On Thu, Nov 27, 2003 at 08:08:05PM -0800, Paul Hodges wrote:
:
: --- Larry Wall <[EMAIL PROTECTED]> wrote:
: > ... in fact, we may be limiting the creation of properties
: > to predeclared names, so that even
: >
: > return 0 but ture;
: >
: > can be caught at compile time.
:
: Excellent, s
--- Larry Wall <[EMAIL PROTECTED]> wrote:
> ... in fact, we may be limiting the creation of properties
> to predeclared names, so that even
>
> return 0 but ture;
>
> can be caught at compile time.
Excellent, so long as we can define new properties explicitly.
At the moment, I draw a comple
[EMAIL PROTECTED] (Larry Wall) writes:
> P.S. I think we deserve a $rubyometer-- for bypassing mixins.
I think you deserve loud and wild applause for an object model I want
to use Right Now Dammit.
--
Overall there is a smell of fried onions. (fnord)
On Thu, Nov 27, 2003 at 12:02:30AM -0700, Luke Palmer wrote:
: Here's a series of questions/confirmation requests about how properties
: work (but specifically run-time properties, not traits):
:
: Use C to assign a property to a I:
:
: $a = $b but foo; # $a has property foo, $b does no
On Wed, Nov 26, 2003 at 03:56:28PM -0500, Mark J. Reed wrote:
> Nicer it may be, But I use File::Find *because* it's in the core,
> so I don't have to worry about my programs being non-portable because I
> use a module that may not be installed.
Of course with Perl 6 modules will be MUCH easier
Here's a series of questions/confirmation requests about how properties
work (but specifically run-time properties, not traits):
Use C to assign a property to a I:
$a = $b but foo; # $a has property foo, $b does not
Properties are just out-of-band methods:
if $x.foo { print "$x ha
