I have been trying to track down why the above prototype is not present in the
AT&T 3.0 specifications for ostreams.  I realize that given the presence of --

 ostream& operator<<(void*);

means that the insertion of a trivial cast will remedy the problem, but it
really isn't a good idea to cast off the constant-ness of objects.  Any
suggestions will be appreciated.
--
jamesh@borland.com