On Sat, 2003-12-13 at 13:48, Jon A. Cruz wrote:
First, I noticed that it has introduced mixed-case filenames. Do we care?
Not until we have an agreed-upon coding standard that specifies whether mixed-case filenames are good or bad.
(I personally prefer naming files after the class/namespace they implement, case and all, though.)
Also, I'm getting a slew of these:
/usr/include/c++/3.2/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <sstream> instead of the deprecated header <strstream.h>. To disable this warning use -Wno-deprecated.
In the cases I've checked, this is due to including <iostream.h> instead of <iostream>
We should probably clean this up. IIRC, the main difference is the namespace issue.
Feel free to do so.
-mental