If you have to write nonportable code, take the following steps (a Taligent engineer must first clear it with an architect):
Contact Taligent for detailed guidelines.
- Clearly mark the code with a comment indicating it is nonportable.
//??? NOT PORTABLE
It is then easy to find such constructs with a global search.
- Identify the environment for which the code is specific.
- Include the name of the processor family somewhere in the filename, such as
FooClassRS6000.C, if the entire file is processor dependent.
Click the icon to mail questions or corrections about this material to Taligent personnel.
Copyright©1995 Taligent,Inc. All rights reserved.
Generated with WebMaker