Hello Craig,

On Jan 27 15:52 96, Craig Swanson of 1:202/354 wrote:

 CS> I find it possible to use VAC++ 3.0, but WF/2 3.0 is by far 

i concur. 

 CS> I've been trying to make use of precompiled headers, but 
 CS> frankly it seems as if I have to change all my source code 

also ok. i've discussed this point in the CIS:VACPP area. 'precompiled
headers unusable new'. 

 CS> to really make them work properly as they are very 
 CS> different from precompiled headers in C Set++ 2.x.  

totally.

 CS> Reorganizing all the header files and changing the *.cpp 
 CS> files that include them is a pretty big task -- I've got 
 CS> several hundred files to change.

We have more then 5000 files (120MB source). :-( 

 CS> As far as a wishlist for future VAC++ versions goes, here 
 CS> is mine:

 CS> 1) Get rid of WF/2.  Replace it with Taligent cpProfessional or something 

i concur.

 CS> 3) Add support for "long long" and "unsigned long long" 
 CS> 4) Add support for in-line assembler

mine MOST important request : Make the compiler again a state of the art
C++ compiler. VACPP is the ONLY (!!!) OS/2 C++ compiler which DOES NOT
conform to the current C++ standard. 

NO RTTI
NO STL
NO NameSpace
NO std-types
........ (long list)
 WARPED!, Mario

--- Msgedsq/2 2.2e