Klaas-Jan Stol wrote:
Allison:
I made the following changes in pirc/new:
.arg - .set_arg
.result - .get_result
.return - .tailcall (in context of .return foo() , which thus is now:
.tailcall foo() )
.return - .set_return (in long-style returning : .begin/end_return
.yield - .set_yield ( in
On Sat, Aug 30, 2008 at 10:40 AM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol wrote:
On Sat, Aug 30, 2008 at 11:04 AM, Allison Randal [EMAIL PROTECTED]
wrote:
Yes, it will be deprecated, or at least renamed. The C.return
directive
without parentheses is an old convention for
On Sat, Aug 30, 2008 at 11:04 AM, Allison Randal [EMAIL PROTECTED] wrote:
Klaas-Jan Stol (via RT) wrote:
The parentheses surrounding the arguments are mandatory. Besides making
sequence break more conspicuous, this is necessary to distinguish this
syntax from other uses of the C.return
Klaas-Jan Stol (via RT) wrote:
The parentheses surrounding the arguments are mandatory. Besides making
sequence break more conspicuous, this is necessary to distinguish this
syntax from other uses of the C.return directive that will be probably
deprecated.
The open issue of the 'probably
Klaas-Jan Stol wrote:
On Sat, Aug 30, 2008 at 11:04 AM, Allison Randal [EMAIL PROTECTED] wrote:
Yes, it will be deprecated, or at least renamed. The C.return directive
without parentheses is an old convention for passing a single return result,
and must always be sandwiched between
# New Ticket Created by Klaas-Jan Stol
# Please include the string: [perl #58236]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58236
PDD19, line 791 reads:
The parentheses surrounding the arguments are mandatory.
