From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: weis Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id RAA09177 for caml-redistribution; Thu, 13 Jan 2000 17:28:17 +0100 (MET) 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 EAA27237 for ; Thu, 13 Jan 2000 04:53:35 +0100 (MET) Received: from cepheus.azstarnet.com (cepheus.azstarnet.com [169.197.56.195]) by nez-perce.inria.fr (8.8.7/8.8.7) with ESMTP id EAA20816 for ; Thu, 13 Jan 2000 04:53:34 +0100 (MET) Received: from vega (dialup10ip008.tus.azstarnet.com [169.197.34.136]) by cepheus.azstarnet.com (8.9.3+blt.Beta0/8.9.3) with SMTP id UAA13147 for ; Wed, 12 Jan 2000 20:53:20 -0700 (MST) X-Sent-via: StarNet http://www.azstarnet.com/ Message-ID: <001501bf5d79$ce98a740$250148bf@vega> From: "David McClain" To: Subject: Secrets of OCAML Date: Wed, 12 Jan 2000 20:53:32 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: weis It may not seem obvious until you try to implement similar functionality in a language of your own. But the need to prefix a label with the module name derives from the simple fact that the module is the place where the label is defined... After you realize that, it is a simple matter to create compound names of any depth crossing any number of module boundaries in the process. Unless a module is "Used" in the sense of importing all of its symbols into your current module, you must refer via the definining module name. It really is quite simple after all... - DM