5.1. What’s New in 4.5.0

This section describes what’s new in Code Generator 4.5.0 (Connext 7.5.0) compared to release 4.4.0 (Connext 7.4.0).

Connext 7.5.0 is an early access release. See the Connext Versions and Lifecycle page for more information on RTI’s software release model.

For what’s new and fixed in other products in the Connext suite, see those products’ release notes on the RTI Community Portal or in your installation.

5.1.1. Added support for range annotations in Python code generation

Support for range annotations (@min, @max, and @range) in Python code generation enhances the ability to define constraints on numerical parameters within the Python API.

5.1.2. Generate a single Python output file, simplifying Python code management

A new command-line option, -joinInputFiles, joins input files and included files, processing them together to create just one output file that contains all the generated Python code. This option is only valid for Python code generation.

This option is useful for consolidating generated code and dependencies into a single location, especially when working with complex projects involving multiple included files. It reduces the complexity of managing imports and file dependencies, and makes it easier to distribute or deploy generated Python code as a standalone module.

Another new command-line option, -joinedInputFilesOutputName <name>, allows you to specify the output file name you want for Python. You can optionally use this together with -joinInputFiles.

For details, see Command-Line Arguments for rtiddsgen in the RTI Code Generator User’s Manual.

5.1.3. Added support for documentation annotation in IDL files

This release adds support for the @doc annotation, which will be added to the OMG standard in future. This annotation can be used to add documentation text for any IDL entity. Use it to add comments, notes, instructions, or other helpful content directly within an IDL file.

The @doc annotation includes two parameters: the value with the documentation and, optionally, the text format. For example:

@doc(“This is the documentation”)

@doc(value="This is the documentation”, format="markdown”)

For details, see Using Builtin Annotations in the RTI Connext Core Libraries User’s Manual.

5.1.4. Added support for licensing annotations in IDL files

This release adds support for the annotations @license, @license_type, and @licencse_use, which will be added in the OMG standard in future. Use them to add licensing information directly within an IDL file.

@license_type defines a license and only applies to modules. It has two parameters: the name of the license and the link to the license legal text. For example:
```
@license_type(name="RTI_EXAMPLE", link="https://community.rti.com/licenses/RTI_EXAMPLE.md")
```
@license_use defines the use of a license type and only applies to modules. It can be a subtype of the license type. It has three parameters: name, a license type that refers to an @license_type (optional), and the link to the legal text of the license. For example:
```
@license_use(name="APACHE2:ROS", license_type="Apache-2.0", link="https://www.osfr.org/ros2/License")``
```
@license defines the license used by modules, aggregation types, enumerators, or aliases. It has a single parameter, the name of the license. For example:
```
@license("RTI_EXAMPLE:AUTOMOTIVE")
```

For details, see Using Builtin Annotations in the RTI Connext Core Libraries User’s Manual.

5.1.5. Deprecations and Removals

This section describes items that are deprecated or removed in 7.5.0, compared to 7.4.0.

Deprecated means that the item is still supported in this release, but will be removed in a future release. Removed means that the item is discontinued or no longer supported.

Any deprecations or removals noted in RTI’s documentation serve as notice under the Real-Time Innovations, Inc., Maintenance Policy #4220 and/or any other agreements by and between RTI and customer regarding maintenance and support of RTI’s software. RTI’s current standard terms and support and maintenance policies are available at https://www.rti.com/terms.

5.1.5.1. Deprecated the use of XSD files as rtiddsgen input

XML Schema files (XSD) can no longer be used as Code Generator input files; this feature has been deprecated. The input will still be valid, but Code Generator will display a warning. The use of XSD files to generate code will be removed in a future release.