From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id KAA27154 for caml-redistribution; Mon, 29 Mar 1999 10:09:19 +0200 (MET DST) Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id TAA00125 for ; Sat, 27 Mar 1999 19:04:36 +0100 (MET) Received: from hadar.cse.Buffalo.EDU (hadar.cse.Buffalo.EDU [128.205.32.1]) by nez-perce.inria.fr (8.8.7/8.8.7) with ESMTP id TAA08360 for ; Sat, 27 Mar 1999 19:04:34 +0100 (MET) Received: (from whitley@localhost) by hadar.cse.Buffalo.EDU (8.8.8/8.8.5) id NAA08329; Sat, 27 Mar 1999 13:04:33 -0500 (EST) From: John Whitley MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 27 Mar 1999 13:04:33 -0500 (EST) To: caml-list@inria.fr Subject: initialization of instance variables X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14077.2636.294799.938058@hadar.cse.Buffalo.EDU> Sender: weis I'm curious as to why class instance variable definitions cannot be used in following instance variable definitions, only in methods and initializers. Is this an implmentation-driven restriction, or is there some more subtle semantics-based reason to prevent this? -- John