On Thursday 23 November 2006 08:48, Patrick R. Michaud wrote:
> Here's a more detailed use case of why the current semantics
> aren't useful. For subroutine calls, PAST-pm tries to pass
> constants directly to subroutines (when it can) rather than
> creating temporary PMCs and passing those. For
From: Allison Randal <[EMAIL PROTECTED]>
Date: Wed, 22 Nov 2006 20:37:26 -0800
Ben Morrow wrote:
>
> ...but that's just a braino on Matt's part, and his point still stands
> for the code
>
> package Test;
>
> sub apply {
> my $func = shift;
Allison Randal <[EMAIL PROTECTED]> wrote:
Okay, so we're basically solving the same problem as Perl 5's "main"
routine, which it stuffs in an obscure C variable internal to the
interpreter, not accessible from the symbol table. (Talk about
less-than-transparent introspection.)
Huh. I don't know
On Wed, Nov 22, 2006 at 11:20:58PM +0100, Leopold Toetsch wrote:
> Am Mittwoch, 22. November 2006 21:03 schrieb Leopold Toetsch:
> > Am Mittwoch, 22. November 2006 18:03 schrieb Patrick R.Michaud:
> > > Is this a bug (I think it is), or does the underscore in
> > >
> > > :multi mean something other
Author: larry
Date: Thu Nov 23 08:46:49 2006
New Revision: 13480
Modified:
doc/trunk/design/syn/S02.pod
Log:
Clarification that unspace is not allowed within tokens, asked by anatoly++.
Modified: doc/trunk/design/syn/S02.pod
===
HaloO,
Adriano Rodrigues wrote:
And we may argue as well that being Bag a multiset, the set is a
special case where all the elements have the same multiplicity.
Yes, that would be a subset type. The thing I had in mind was
'role Seq does Bag' and 'role Bag does Set'. And classes with
the same
On 11/23/06, TSa <[EMAIL PROTECTED]> wrote:
HaloO,
Darren Duncan wrote:
> And if Seq and Set etc are interchangeable for all situations where it
> doesn't matter whether the elements are ordered or not, then a lot of
> times users won't have to care which they have.
One can argue that we have t
HaloO,
Darren Duncan wrote:
And if Seq and Set etc are interchangeable for all situations where it
doesn't matter whether the elements are ordered or not, then a lot of
times users won't have to care which they have.
One can argue that we have the subtyping chain Seq <: Bag <: Set for
these i
