Richard Proctor <[EMAIL PROTECTED]> writes:
> On Fri 18 May, Damian Conway wrote:
> >
> > Ed wrote:
> >
> >
> >> Can 'undef' valued thingys have properties
> >
> > Yes.
> >
> >> and functions?
> >
> > No.
> >
>
> Why not?
You can always set a property on a function referenc
On Sat, May 19, 2001 at 06:41:29PM +1000, Damian Conway wrote:
>
> Graham wrote:
>
>> On Fri, May 18, 2001 at 10:36:59PM -0400, John Siracusa wrote:
>> > > print keys $foo.prop; # prints "NumberHeard"
>> > > print values $foo.prop; # prints "loneliestever"
>>
>
[EMAIL PROTECTED] writes:
: Graham wrote:
:
:> On Fri, May 18, 2001 at 10:36:59PM -0400, John Siracusa wrote:
:> > > print keys $foo.prop; # prints "NumberHeard"
:> > > print values $foo.prop; # prints "loneliestever"
:>
:> This is an example of one of my co
Graham Barr <[EMAIL PROTECTED]> writes:
> On Fri, May 18, 2001 at 03:01:38PM +1000, Damian Conway wrote:
> >> Also, what's the difference between a 'property' and an
> >> 'attribute', ie, are:
> >>
> >>$fh is true;
> >>
> >> and
> >>
> >>$fh.true(1);
>
Graham Barr <[EMAIL PROTECTED]> writes:
> On Fri, May 18, 2001 at 08:31:21AM -0500, Jarkko Hietaniemi wrote:
> > On Fri, May 18, 2001 at 06:22:10AM -0700, Austin Hastings wrote:
> > >
> > > --- Damian Conway <[EMAIL PROTECTED]> wrote:
> > >
> > > > It's probably just a matter of coding what yo
Buddha Buck wrote:
> Personally, I'd rather save let for:
I appreciate the sentiment, but I believe it's misplaced
and unnecessary.
> (let ($x,$y,$z,...) = (1,2,3,...) in { FOO })
>
> which would be equivilant to:
>
> ((sub {my ($x,$y,$z,...) = @_; FOO })(1,2,3,...))
But it's also equivale
On Fri, May 18, 2001 at 10:36:59PM -0400, John Siracusa wrote:
> > print keys $foo.prop; # prints "NumberHeard"
> > print values $foo.prop; # prints "loneliestever"
This is an example of one of my concerns about namespace overlap
with methods. What would happen if there was a me
At 11:47 AM 5/19/2001 -0700, Larry Wall wrote:
>Edward Peschko writes:
>: Why can't variable properties and value properties be the same thing?
>
>Because a variable is a container, and has properties appropriate to
>a container, and a value is a containee, and has properties appropriate
>to a con
Dan Sugalski wrote:
> So what happens when you assign an overloaded value to a tied variable, or
> vice versa? Which wins?
Uh, the overloaded value gets evaluated to an normal value,
and the tied variable does what it does with that.
Maybe.
--
John Porter
At 02:55 PM 5/19/2001 -0400, John Porter wrote:
>Dan Sugalski wrote:
> > So what happens when you assign an overloaded value to a tied variable, or
> > vice versa? Which wins?
>
>Uh, the overloaded value gets evaluated to an normal value,
>and the tied variable does what it does with that.
>
>Mayb
John Porter writes:
: Buddha Buck wrote:
: > Personally, I'd rather save let for:
:
: I appreciate the sentiment, but I believe it's misplaced
: and unnecessary.
:
:
: > (let ($x,$y,$z,...) = (1,2,3,...) in { FOO })
: >
: > which would be equivilant to:
: >
: > ((sub {my ($x,$y,$z,...) = @_
Dan Sugalski writes:
: At 02:55 PM 5/19/2001 -0400, John Porter wrote:
: >Dan Sugalski wrote:
: > > So what happens when you assign an overloaded value to a tied variable, or
: > > vice versa? Which wins?
: >
: >Uh, the overloaded value gets evaluated to an normal value,
: >and the tied variable d
Edward Peschko writes:
: Why can't variable properties and value properties be the same thing?
Because a variable is a container, and has properties appropriate to
a container, and a value is a containee, and has properties appropriate
to a containee. (Plus, any given value could be in multiple
Piers wrote:
> > >> Can 'undef' valued thingys have properties
> > >
> > > Yes.
> > >
> > >> and functions?
> > >
> > > No.
> > >
> >
> > Why not?
>
> You can always set a property on a function reference. But it seems a
> little weird that
Graham wrote:
> On Fri, May 18, 2001 at 10:36:59PM -0400, John Siracusa wrote:
> > > print keys $foo.prop; # prints "NumberHeard"
> > > print values $foo.prop; # prints "loneliestever"
>
> This is an example of one of my concerns about namespace overlap
> wit
On Sat, May 19, 2001 at 11:47:10AM -0700, Larry Wall wrote:
> Edward Peschko writes:
> : my $num = 0 is true;
> : print $num.true; # prints 1;
>
> You've set a variable property there, so any value in it will appear to
> be permanently true.
My minds wanted that to be a value property. So, is t
> Fine, that's a value property, because $ARGS is a simple scalar
> variable that doesn't particularly care that it's pointing to a magical
> filehandle object.
>
> : my $string = "value";
> : print $string.value; # prints 'value'
>
> That seems a bit odd, since .value is a no-op, unless you wa
At 03:31 AM 5/19/2001 +0100, Simon Cozens wrote:
>On Fri, May 18, 2001 at 06:29:11PM -0700, Daniel S. Wilkerson wrote:
> > Therefore, if it isn't a back-end and it isn't a front-end, what is it?!
>
>Both!
It's a dessert topping *and* a floor wax!
> > Can someone say what it is?
>
>It's true that
Daniel S. Wilkerson writes:
> Therefore, if it isn't a back-end and it isn't a front-end, what is it?!
> Perl6 seems to be a "nothing sandwich". Not that this is bad, Zen is this
> way.
Simon's done a good job of explaining this, but I'll try too.
You're right, we're designing many things. Lar
At 08:57 AM 5/19/2001 -0600, Nathan Torkington wrote:
>The language will stay as "Perl", but the VM might get its own name.
Parrot! ;-P
And I see I need to draw some pictures, since Nat's explanation's not quite
what I'm thinking of at the moment. (Close though) I'll see about getting
somethin
20 matches
Mail list logo
