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,5c72b6fec2f83257 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Help: Binary operator "=" Date: 1997/06/07 Message-ID: #1/1 X-Deja-AN: 246810412 References: <3381c4ba.quantum@quantum.pc.my> <33932325.6E38@lmtas.lmco.com> Organization: New York University Newsgroups: comp.lang.ada Date: 1997-06-07T00:00:00+00:00 List-Id: Ken says < A_Thing.Object, Onto => A_Stack.Object); -- nice if Some_Stack_Type.Is_Empty(A_Stack.Object) ... -- OK if Some_Stack_Type."="(A_Stack.Object, Another_Stack.Object) then ... -- not nearly as nice as if A_Stack.Object = Another_Stack.Object then ... Surely the increased readability is intuitively obvious! :) >> Oh most certainly it is to me, getting rid of the silly Some_Stack_Type prefix on "=" and deciding that you can use other means to figure out where "=" comes from makes excellent sense to me. The only trouble is, I would apply the same reasoning to the annoying Some_Stack_Type. prefix on the Is_Empty call. Indeed I don't see the difference between the two cases. Either it is a problem to have to find out where things are, necessitating the verbose prefixs, or it is not, and the situation seems the same in both cases to me :-) :-) (the smileys are because this is an old discussion, hardlly worth repeating unless someone has something new to say :-)