>As my example demonstrated, it's because there's no run-time
>application of content coercion templates. And I don't think
s/ent/ext/
>Tom Christiansen wrote:
>> > I think it's critical that built-ins be reference-takeable,
>> > just like user-defineds.
>>
>> But they [dw]on't work right.
>Um -- why not? Why can't we make then work right in perl6?
As my example demonstrated, it's because there's no run-time
application of
Tom Christiansen wrote:
> > I think it's critical that built-ins be reference-takeable,
> > just like user-defineds.
>
> But they [dw]on't work right.
Um -- why not? Why can't we make then work right in perl6?
--
John Porter
>Gisle Aas wrote:
>>
>> foo(\&print, "foo");
>I think it's critical that built-ins be reference-takeable,
>just like user-defineds.
But they [dw]on't work right.
sub CORE::push { push(@_);
$fn = \&CORE::push;
$fn->(@some_array, now, some, list);
--tom
Gisle Aas wrote:
>
> foo(\&print, "foo");
I think it's critical that built-ins be reference-takeable,
just like user-defineds.
--
John Porter
No need to send them to -language as well as the librarian. The
librarian assigns a number then posts it to the appropriate list, so
just sending it to the librarian will save the duplication and keep the
discussion more tightly threaded.
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://n
>Johan Vromans <[EMAIL PROTECTED]> writes:
>> =head1 ABSTRACT
>>
>> Perl distinguishes named operators and functions. For Perl6, this
>> disctinction can be dropped.
>Will this then work?
> sub foo {
> my $func = shift;
> &$func(@_);
> }
> foo(\&print, "foo");
> foo("print", "foo"
Johan Vromans <[EMAIL PROTECTED]> writes:
> =head1 ABSTRACT
>
> Perl distinguishes named operators and functions. For Perl6, this
> disctinction can be dropped.
Will this then work?
sub foo {
my $func = shift;
&$func(@_);
}
foo(\&print, "foo");
foo("print", "foo");
foo(\&C
