Newsgroups: perl.perl6.internals
Path: g2news1.google.com!news1.google.com!newsread.com!news-xfer.newsread.com!logbridge.uoregon.edu!newsfeed.stanford.edu!nntp.perl.org
Return-Path: <r...@theworld.com>
Mailing-List: contact perl6-internals-h...@perl.org; run by ezmlm
Delivered-To: mailing list perl6-intern...@perl.org
Delivered-To: moderator for perl6-intern...@perl.org
Received: (qmail 24106 invoked from network); 3 Apr 2005 03:18:41 -0000
Received: from x1a.develooper.com (HELO x1.develooper.com) (216.52.237.111)
  by lists.develooper.com with SMTP; 3 Apr 2005 03:18:41 -0000
Received: (qmail 8456 invoked by uid 225); 3 Apr 2005 03:18:41 -0000
Delivered-To: perl6-intern...@perl.org
Received: (qmail 8447 invoked by alias); 3 Apr 2005 03:18:41 -0000
X-Spam-Status: No, hits=-4.3 required=8.0
	tests=ALL_TRUSTED,BAYES_00,DNS_FROM_RFC_POST
X-Spam-Check-By: la.mx.develooper.com
Received-SPF: neutral (x1.develooper.com: local policy)
Received: from x6.develooper.com (HELO lists.develooper.com) (63.251.223.186)
    by la.mx.develooper.com (qpsmtpd/0.28) with SMTP; Sat, 02 Apr 2005 19:18:39 -0800
Received: (qmail 24098 invoked by uid 515); 3 Apr 2005 03:18:36 -0000
Message-ID: <20050403031836.24097.qmail@lists.develooper.com>
To: perl6-intern...@perl.org
Date: Sat, 02 Apr 2005 22:20:44 -0500
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050109 Debian/1.7.5-0.backports.org.1
X-Accept-Language: en, en-us, en-ca, en-gb, en-au, en-nz, en-ie, fr, es, de, fi
MIME-Version: 1.0
Subject: Re: [PROPOSAL] calling convention abstraction
References: <42492DB9.1020903@toetsch.at>
In-Reply-To: <42492DB9.1020903@toetsch.at>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Posted-By: 209.94.133.172
Approved: n...@nntp.perl.org
From: r...@theworld.com (Roger Hale)

Leopold Toetsch wrote:
> Below inline attached is a scheme for an abstraction layer around 
> calling conventions.
> 
> Comments welcome,
> leo

 > 2.5) return context
 >
 > Yesterdays conversation on IRC (yes!) has clearly shown that the
 > current calling conventions are lacking information about scalar vs
 > list vs void context.
 >
 >   sub foo { want.List ?? (1,2,3) :: 1 }   # or some such
 >
 > This information could also be attached to @ARGS. E.g.
 >
 >   @ARGS."return_list"(1)

Would it be possible to attach it to the continuation?  Then in the 
course of tail-calling the information continues to be available just 
where it's needed.