Introducing SAS/C Software, Release 6.50

SAS/C C++ Development System

The SAS/C C++ Development System is an add-on product that extends the capabilities of the base SAS/C product, enabling you to develop and run C++ programs on the mainframe under TSO, CMS, MVS batch, the OpenEdition shell, and CICS. The system implements the C++ language by means of a translator that translates C++ to C. The translated C code must be compiled with the SAS/C Compiler, resulting in an object module. By default, when you invoke the translator, both the translation and compilation are performed; that is, you do not have to call the SAS/C Compiler as a separate step.

The C++ language accepted by the SAS/C C++ Development System is generally compatible with that specified by Bjarne Stroustrup in the The C++ Programming Language, Second Edition, except that several ANSI C++ features have been added and exception handling has not been implemented. Code written for previous releases of the SAS/C C++ Development System will also generally be accepted by this release. However, this release has increased compatibility with the ANSI/ISO C++ draft standard by implementing new features and by tightening language rules for certain obscure or unsafe constructs.

Release 6.50 of the SAS/C C++ Development System includes these new features:

template support
new cast operators
run-time type identification
overload resolution rules updated for clarity.

If you have a C++ program that is compliant with AT&T C++ version 3.0, your code should generally work with the SAS/C C++ Development System.

If you have a C++ program that is compliant with AT&T C++ version 2.1, with the exception of some features that are now considered outdated, your code should generally work with the SAS/C C++ Development System. The main differences between AT&T C++ 2.1 and the SAS/C C++ Development System are the following:

SAS/C C++ does not support overloading both the prefix and postfix ++ or -- operators with a single function.
SAS/C C++ does not support the transitional model of nested classes. That is, a class that is nested is always treated as nested, even if there is not a file-scope class of the same name.

Chapter Contents
Previous
Next
Top of Page