From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id RAA13475; Fri, 20 Jul 2001 17:37:51 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id RAA13470 for ; Fri, 20 Jul 2001 17:37:50 +0200 (MET DST) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by concorde.inria.fr (8.11.1/8.10.0) with ESMTP id f6KFbfb26472; Fri, 20 Jul 2001 17:37:41 +0200 (MET DST) Received: (from xleroy@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id RAA13465; Fri, 20 Jul 2001 17:37:40 +0200 (MET DST) Date: Fri, 20 Jul 2001 17:37:40 +0200 From: Xavier Leroy To: "Krishnaswami, Neel" Cc: "'caml-list@inria.fr'" Subject: Re: [Caml-list] Are multiple return values optimized? Message-ID: <20010720173740.E12623@pauillac.inria.fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from neelk@cswcasa.com on Mon, Jul 16, 2001 at 04:33:38PM -0400 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk > Are multiple return values optimized to avoid heap-allocation > like curried functions are? No, a tuple of results is always heap-allocated. However, with Caml's generational GC, the cost of allocating such short-lived tuples is quite low. - Xavier Leroy ------------------- Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr