Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!ucbvax!ulysses!hector!jss
From: jss@hector.UUCP (Jerry Schwarz)
Newsgroups: comp.lang.c++
Subject: Re: C++ textbooks (was: C++ design)
Keywords: information
Message-ID: <11700@ulysses.homer.nj.att.com>
Date: 26 Jun 89 15:19:31 GMT
References: <9474@alice.UUCP> <916@tukki.jyu.fi> <137@ssp1.idca.tds.philips.nl> <550@cpsc6b.cpsc6a.att.com> <Jun.21.20.51.33.1989.27612@galaxy.rutgers.edu>
Sender: netnews@ulysses.homer.nj.att.com
Reply-To: jss@hector.UUCP (Jerry Schwarz)
Organization: AT&T Bell Laboratories
Lines: 14

In article <Jun.21.20.51.33.1989.27612@galaxy.rutgers.edu> pete@andromeda.rutgers.edu.UUCP (Peter Farabaugh) writes:
>	I think that referring to the << and >> operators as put to and get
>from is a good idea. Shift left and right is to confusing and less-than-sign-
>less-than-sign, greater-than-sign-greater-than-sign is stupid. 

For the record, the 2.0 iostream documentation (which I had a part in
writing) refers to << and >> as insertion and extraction operators
repsectively, and to the variants for a particular type T as the T
insertor and T extractor.

I find this terminology clear and concise.  I hope it catches on.

Jerry Schwarz
AT&T Bell Labs, Murray Hill