🚀 go-pugleaf

jbuck@forney.berkeley.edu (Joe Buck) writes:
: In article <1992Aug31.164909.7198@fcom.cc.utah.edu> swillden@news.ccutah.edu (Shawn Willden) writes:
: 

[ My questions and Joe's informative responses deleted ]

: >4)	How standard are the libg++ libraries?  (i.e. how closely do they track
: >the work of the ANSI C++ committee? [In implementation, not content, ANSI
: >hasn't/isn't going to specify standard libraries, right?])
: 
: As of libg++ 2.0, the iostream library is very close to that of AT&T.
: Yes, ANSI is going to specify standard libraries for streams, and possibly
: a couple of others.  I think you mean "In interface, not implementation",
: since you don't care about the implementation if the interface is the same.

Actually, I meant more or less what I said.  Since I didn't believe that
ANSI was going to specify any standard libraries (I should have realized 
that streams would be specified) I didn't expect that libg++ would have any
kind of a standard interface.  By 'implementation' I meant design and 
coding rather than the traditional OOP sense of the word.  What I *should*
have said is "Given an ANSI-conformant compiler (conformant to whatever
degree it has been defined) can I expect the libg++ libraries to compile
on it?".  Thanks for the correction.  Oh, and BTW, you mention a 'couple of
others' (library classes), what are they?
 
: >5)	Is 2.2.2 compatible with the NeXT gdb or would I have to get gdb-4.6 as
: >well?
: 
: I recommend getting gdb-4.6 if you're going to use g++.  It has greatly
: improved facilities for finding member functions, including command
: completion (where you type part of the name and prototype of an overloaded
: member function and it completes it or lists the possibilities).  I don't
: know what version of gdb NeXT provides; if it predates 4.0 you'll need
: to upgrade.
: 
: --
: Joe Buck	jbuck@ohm.berkeley.edu

Thanks, Joe.

--
Shawn Willden
swillden@icarus.weber.edu