In contrast to return values, it may be helpful to use size_t type for function parameters that represent sizes or dimensions of objects. Using size_t lets callers pass either unsigned or size_t arguments without warnings. While this minimizes impact on existing code, it relies on the function to raise an assert, or throw an exception when an unexpected value is passed in. If a function needs to impose a 32-bit limit internally, it can assert that the size_t value is less than 4GB before using the argument as a 32-bit value. This practice is not recommended, as it avoids compile time checks, and increases the risk of runtime errors.
- Customization and Administration Guides
- DXF Reference
- AutoLISP and DCL
- ActiveX and VBA
- ObjectARX and Managed .NET
- ObjectARX: Developer's Guide
- ObjectARX: Reference Guide
- ObjectARX: Managed .NET Developer's Guide
- ObjectARX: Managed .NET Reference Guide
- ObjectARX: Interoperability Guide
- ObjectARX: Migration Guide
- General Development Compatibility (ObjectARX/.NET)
- Migrate from AutoCAD 2024 and Earlier
- Migrate from AutoCAD 2023 and Earlier
- Migrate from AutoCAD 2022 and Earlier
- Migrate from AutoCAD 2020 and Earlier
- Migrate from AutoCAD 2018 and Earlier
- Removal of Header Files (ObjectARX)
- Graphics System Changes (ObjectARX)
- Handling the New Tab Page (ObjectARX/.NET)
- 64-bit Migration Guide
- ObjectARX: Release Notes
- JavaScript
- AutoCAD Core Console