From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,9cccf6ef6149fdaa
X-Google-Attributes: gid103376,public
From: "Samuel T. Harris" <samuel_t_harris@Raytheon.com>
Subject: Re: Operators -> unit analysis
Date: 2000/01/06
Message-ID: <3874D0BE.82F04763@Raytheon.com>#1/1
X-Deja-AN: 569163849
Content-Transfer-Encoding: 7bit
References: <38620350.48F8FC08@gecm.com> <83u8l0$5i5$1@nnrp1.deja.com>
 <84rd2f$snm$1@nntp3.atl.mindspring.net> <t7aemmtz3b.fsf@calumny.jyacc.com>
 <84thof$9r3$1@nntp4.atl.mindspring.net> <387383D0.4EA02E95@earthlink.net>
 <850jiq$mad$1@nnrp1.deja.com>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
Organization: Raytheon Aerospace Engineering Services
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 2000-01-06T00:00:00+00:00
List-Id: <comp.lang.ada>

Ted Dennison wrote:
> 
> In article <387383D0.4EA02E95@earthlink.net>,
>   Charles Hixson <charleshixsn@earthlink.net> wrote:
> > Terry Sikes wrote:
> >
> > > ...
> > > One thing I'd like to see in both languages is the ability to use a
> > > set of non-reserved Unicode symbols for operator overloading, to
> > > disambiguate with the normal operator symbols.
> 
> > I don't insist on unicode, but I would also like more operators that
> > could be overloaded.
> 
> How would you decide where to place them in the precidence hierarchy?
> Having recently built a couple of packages around overloaded operators,
> I found that getting the correct precidence for the various new
> operators I defined is at least as important as the appropriateness of
> the chosen operator symbol to the task. You don't want to end up in a
> situation where you have to use parenthesis in counter-intuitive places
> to work around the precidence rules.
> 

How about a representation clause which defines the precedence
of a custom operator to that of another. Something like ...

for "union"'precedence use "+";
for "intersection"'precedence use "*";

-- 
Samuel T. Harris, Principal Engineer
Raytheon, Aerospace Engineering Services
"If you can make it, We can fake it!"