Return-Path: <john.harrison-request@uk.ac.cam.cl>
Delivery-Date: 
Received: from ted.cs.uidaho.edu by swan.cl.cam.ac.uk with SMTP (PP-6.0) 
          id <06018-0@swan.cl.cam.ac.uk>; Tue, 7 Jul 1992 23:36:34 +0100
Received: by ted.cs.uidaho.edu (16.6/1.34) id AA04604;
          Tue, 7 Jul 92 15:17:02 -0700
Sender: info-hol-request@edu.uidaho.cs.ted
Errors-To: info-hol-request@edu.uidaho.cs.ted
Received: from panther.cs.uidaho.edu by ted.cs.uidaho.edu (16.6/1.34) 
          id AA04599; Tue, 7 Jul 92 15:16:59 -0700
Received: from localhost by panther.cs.uidaho.edu with SMTP 
          id AA22092 (5.65c/IDA-1.4.4 for info-hol@cs.uidaho.edu);
          Tue, 7 Jul 1992 15:23:26 -0700
Message-Id: <199207072223.AA22092@panther.cs.uidaho.edu>
To: info-hol@edu.uidaho.cs.ted
Subject: Re: constant name reuse
In-Reply-To: Your message of 07 Jul 92 15:07:00 -0700. <475*sree@cs.ubc.ca>
Date: Tue, 07 Jul 92 15:23:25 -0700
From: Phil Windley <windley@edu.uidaho.cs.panther>
X-Mts: smtp


On 07 Jul 92 15:07:00 PDT, sree@cs.ubc.ca wrote:
+------------
| The problem came up when trying to use two libraries at the same time:
| "auxiliary" and "group" - there is a constant "INV" defined in both of them,
| and so loading fails complaining of constant redefinition.
| I was wondering if there is a solution (other than the obvious) for this:

I've wondered about overloading in the past as well.  Usually, I pass it
off as just a nicety that I can do without by making names unique, but
Sreeranga brings up a very good reason for allowing overloading: libraries.

Couldn't the overloading be done in parsing/pretty printing (i.e.
extralogical)?

Phillip J. Windley, Asst. Professor   |  windley@cs.uidaho.edu
Laboratory for Applied Logic	      |  windley@panther.cs.uidaho.edu
Department of Computer Science        |
University of Idaho                   |  Phone: 208.885.6501  
Moscow, ID    83843                   |  Fax:   208.885.6645

