Subroutines calls should interpolate in double-quoted strings and similar
contexts.
print "Sunset today is at sunset($date)";
interpolates to:
print 'Sunset today is at '.sunset($date);
Huh? And what if it's a built-in? What if it's not quite a built-in,
but an import? What if you
Surely the next request will be to make anything that works outside
of quotes work inside of them, completely erasing the useful visual
distinction. Why should operators, after all, be any different
from functions?
print "I have Fooey-fright($n) frobbles.\n";
print "I have snaggle($n)
On Mon, Sep 18, 2000 at 01:16:43AM -0600, Tom Christiansen wrote:
Huh? And what if it's a built-in? What if it's not quite a built-in,
but an import? What if you don't *know* whether it's a built-in?
Easy enough, built-ins shouldn't be special (I'm speaking in general,
not just when
Tom Christiansen wrote:
And what if it's a built-in? What if it's not quite a built-in,
but an import? What if you don't *know* whether it's a built-in?
I would hope that the distinction (at the syntactic level) goes away.
(Except for the small set of exceptional built-ins, which clearly
Perl6 RFC Librarian wrote:
The is mandatory.
Which makes me happy with this proposal
Parens are also mandatory if
arguments are to be passed.
And I guess the balancing of the parens would solve many of the problems of
argument parsing for the function, which is a concern to me. Within
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Interpolation of subroutines
=head1 VERSION
Maintainer: Michael G Schwern [EMAIL PROTECTED]
Date: 17 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 252
Version: 1
Status: Developing
=head1
