CAD Exchanger SDK
|Single namespace||All C++ classes are defined in the cadex namespace|
Each API class is defined in a header file with the same name and located in the cadex subdirectory. Thus, for instance, the header file for an IGES reader should be included as follows:
|Format naming||Classes that relate to a specific format have a prefix corresponding to that format (e.g. STEP_, JT_).|
|Conversion naming||Classes that perform import of CAD files (i.e. parsing and converting them into CAD Exchanger data model) have a suffix Reader (e.g. ACIS_Reader, JT_Reader), those which perform export (i.e. converting from CAD Exchanger data model and saving to a file) have a suffix Writer (e.g. STEP_Writer, Para_Writer).|
|Data model classes naming||Classes related to CAD Exchanger data model have a prefix ModelData_ (e.g. ModelData_Part, ModelData_Body).|
|Debug and release naming||CAD Exchanger SDK libraries are shipped for both release and debug modes. The API debug libraries have suffix 'd' in their names (e.g. CadExIGESd.lib) and are located in the ./bind and ./libd subdirectories.|
|Easy library linking|
On Windows linking with SDK import libraries (.lib) is done automatically when including a respective header file. For instance, including JT_Reader.hxx will automatically link with CadExJT.lib (in release mode) or CadExJTd.lib (in debug mode). This allows to avoid explicit linking (e.g. via Visual Studio project settings).
On other platforms you may need to explicitly link to the SDK libraries. Remember to link to different libraries, depending whether you compile for debug or release mode.