- Original Message
From: David Green david.gr...@telus.net
I suppose, but is there a reason why you want to apply roles instead of
coercing
the results?
$x = Role::Serializable::XML $resultset;
$y = Role::Serializable::YAML $resultset;
Because I am coming from Moose
On Thu, Mar 12, 2009 at 08:51:45AM -0700, Ovid wrote:
:
: - Original Message
:
: From: David Green david.gr...@telus.net
:
: I suppose, but is there a reason why you want to apply roles instead of
coercing
: the results?
:
: $x = Role::Serializable::XML $resultset;
:
Em Qui, 2009-03-12 às 10:28 -0700, Larry Wall escreveu:
On Thu, Mar 12, 2009 at 08:51:45AM -0700, Ovid wrote:
: From: David Green david.gr...@telus.net
: I suppose, but is there a reason why you want to apply roles instead of
coercing
: the results?
: Because I am coming from Moose
Daniel Ruoso wrote:
Em Qui, 2009-03-12 às 10:28 -0700, Larry Wall escreveu:
On Thu, Mar 12, 2009 at 08:51:45AM -0700, Ovid wrote:
: From: David Green david.gr...@telus.net
: I suppose, but is there a reason why you want to apply roles instead of coercing
: the results?
: Because I am
Em Qui, 2009-03-12 às 19:07 +0100, Jonathan Worthington escreveu:
IIRC, that's a special syntactic form that only counts when it is on the
RHS of but or does. (And yes, in this case it fails if the role has more
than one attr...) I think in all other cases, it's a coercion.
hmm...
for some
On Thu, Mar 12, 2009 at 03:05:17PM -0300, Daniel Ruoso wrote:
: Em Qui, 2009-03-12 às 10:28 -0700, Larry Wall escreveu:
: On Thu, Mar 12, 2009 at 08:51:45AM -0700, Ovid wrote:
: : From: David Green david.gr...@telus.net
: : I suppose, but is there a reason why you want to apply roles instead
On Thu, Mar 12, 2009 at 03:29:09PM -0300, Daniel Ruoso wrote:
: Em Qui, 2009-03-12 às 19:07 +0100, Jonathan Worthington escreveu:
: IIRC, that's a special syntactic form that only counts when it is on the
: RHS of but or does. (And yes, in this case it fails if the role has more
: than one
Em Qui, 2009-03-12 às 11:49 -0700, Larry Wall escreveu:
In addition to what Jonathan said, it is possible that the ability
to coerce multiple arguments depends on the type itself, since we
probably want to allow Foo(1,2,3) and such for listy types that
don't necessarily want to use the [1,2,3]
Larry Wall wrote:
Note however that coercions require parens these days, since types parse
as values, not as routine names.
$x = Role::Serializable::XML($resultset);
$y = Role::Serializable::YAML($resultset);
Should indirect object syntax work in this context?:
$a = Foo: $value;
Author: lwall
Date: 2009-03-12 22:30:47 +0100 (Thu, 12 Mar 2009)
New Revision: 25807
Modified:
docs/Perl6/Spec/S03-operators.pod
Log:
Clarify value syntax inconsistency noticed by pmichaud++
Modified: docs/Perl6/Spec/S03-operators.pod
On Thu, Mar 12, 2009 at 01:38:30PM -0700, Dave Whipp wrote:
Larry Wall wrote:
Note however that coercions require parens these days, since types parse
as values, not as routine names.
$x = Role::Serializable::XML($resultset);
$y = Role::Serializable::YAML($resultset);
Should
In the spectest suite (specifically in: t/spec/S32-array/kv.t), the last
several tests seem to be testing for named arguments to kv:
# check the non-invocant form with named arguments
my @array = a b c d;
my @kv = kv(:array(@array));
#?rakudo skip 'named args'
is(+...@kv,
Hi,
Cory Spencer wrote:
In the spectest suite (specifically in: t/spec/S32-array/kv.t), the last
several tests seem to be testing for named arguments to kv:
# check the non-invocant form with named arguments
my @array = a b c d;
my @kv = kv(:array(@array));
#?rakudo
On Thu, Mar 12, 2009 at 04:03:15PM -0300, Daniel Ruoso wrote:
: Em Qui, 2009-03-12 às 11:49 -0700, Larry Wall escreveu:
: In addition to what Jonathan said, it is possible that the ability
: to coerce multiple arguments depends on the type itself, since we
: probably want to allow Foo(1,2,3)
I have a quick question about the Str type, described in Synopsis 2:
Str Perl string (finite sequence of Unicode characters)
Specifically, and partly in the interest in future-proofing, is there support in
Str for representing codepoint numbers that are beyond the range currently
+To declare an item that is parsed as a simple term, you must use the
+form C term:foo , or some other form of constant declaration such
+as an enum declaration. Such a term never looks for its arguments,
+is never considered a list prefix operator, and may not work with
+subsequent
Actually, never mind. For my purposes, I'll just pretend that Str is that
flexible, since going beyond the Unicode range is more of an academic
possibility than something likely to happen much in real use. Or if it does
happen, I'll adapt later. So no need to reply. Thank you. -- Darren
Author: lwall
Date: 2009-03-13 00:15:48 +0100 (Fri, 13 Mar 2009)
New Revision: 25809
Modified:
docs/Perl6/Spec/S02-bits.pod
docs/Perl6/Spec/S03-operators.pod
docs/Perl6/Spec/S04-control.pod
docs/Perl6/Spec/S12-objects.pod
src/perl6/STD.pm
t/perl5/roundtrip.t
18 matches
Mail list logo
