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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!pyrnj!mirror!gabriel!ada-uts!stt
From: stt@ada-uts
Newsgroups: comp.lang.ada
Subject: Re: Overloading "and"
Message-ID: <4700083@ada-uts>
Date: Thu, 6-Nov-86 10:47:00 EST
Article-I.D.: ada-uts.4700083
Posted: Thu Nov  6 10:47:00 1986
Date-Received: Mon, 10-Nov-86 22:06:06 EST
References: <1146@ucbvax.berkeley.edu>
Nf-ID: #R:ucbvax.berkeley.edu:-114600:ada-uts:4700083:000:555
Nf-From: ada-uts!stt    Nov  6 10:47:00 1986
List-Id: <comp.lang.ada>


It is illegal to overload "and then" and "or else" (as these
are "operations" but not "operators"), but it is
perfectly legal to overload the logical operators "and,"
"or," and "xor."

The only restriction about overloading operators has to
do with "=" and "/=."  You may not separately overload "/=,"
and you may only define "=" for limited types, or by renaming
another "=."   Thanks to generics, you can in fact
define "=" for any type by doing so in an instantiation
of a generic passing the type as the actual matching a formal
limited private type.