🚀 go-pugleaf

In article <3vqnqf$kst@hardcopy.ny.jpmorgan.com>,
Joe Borkoles  <jborkole@jpmorgan.com> wrote:
>mfinney@inmind.com wrote:
>>In the 28 April 1995 Draft Standard (which I was only able to download last week)
>>section 20.2.1 says that the STL portion of the Standard Library will define
>>operator!=(), operator>(), operator<=() and operator>=() in terms of operator=()
>>and operator<().
>>
>>This breaks my code!  And NOT in a fixable fashion!
>>
>
>I too have been finding these operators quite annoying and forcing me to reorder my
>header files in a most unpleasant fashion. I have had some discussion with
>colleagues and we thought that breaking up the standard library into 
>hierarchical namespaces might be the way to go.

	I simply deleted the templates from the STL files.
No part of the HP STL implementation I have used so far uses
these templates -- but I may have missed something.

	This won't be necessary with an ISO Standard C++
compiler because of several new rules on lookup and overloading.

	I dislike the defaulting to the total order, but C++
doesn't contain sufficient functionality to declare, on a class
by class basis, that some members (friends) should be defined based on
a model. Macros still remain the simplest way to do this. :-(
Global defaults is a very second rate solution, but arguably
better than macros :-)


--
        JOHN (MAX) SKALLER,         INTERNET:maxtal@suphys.physics.su.oz.au
	Maxtal Pty Ltd,		    
        81A Glebe Point Rd, GLEBE   Mem: SA IT/9/22,SC22/WG21 
        NSW 2037, AUSTRALIA	    Phone: 61-2-566-2189