Target Language Compiler

Compatibility Issues

Compatibility Issues in Version 5.0

In bringing Target Language Compiler files from Release 12.1 to Release 13, the following changes may affect your TLC codebase:

• The BlockInstanceData function, as mentioned above, has been deprecated. Any TLC files that reference it should be updated.
• By default, GRT targets now use the rtModel data structure in place of the root SimStruct.

• Designed to reduce code size and improve readability, the rtModel is a lightweight structure that is dynamically created when compiling a model, containing only those fields required to execute that model. GRT now utilizes the SimStruct only for noninlined child S-functions.

• Changes to the format of the model.rtw file may require you to update TLC files that access model.rtw records, especially if they do so directly rather than by calls to the TLC function library.

Compatibility Issues in Version 4.1

In bringing Target Language Compiler files from Release 12 to Release 12.1, the following changes may affect your TLC codebase:

• The formats and default values for several important record structures in the model.rtw file have been changed. See model.rtw Changes Between Real-Time Workshop 5.0 and 4.1 for further information.
• During the initialization phase of code generation, the order in which the Target Language Compiler calls each block's BlockTypeSetup and BlockInstanceSetup functions is different. In version 4.1, the BlockTypeSetup function is called before the BlockInstanceSetup function.
• The code generation variables FunctionInlineType and PragmaInlineString are now obsolete.

Compatibility Issues in Version 4.0

In bringing Target Language Compiler files from Release 11 to Release 12, the following changes may affect your TLC codebase:

• Nested evaluations are no longer supported. Expressions such as

• %<LibBlockParameterValue(%<myVariable>,"", "", "")>
  

• are no longer supported. You will have to convert these expressions into equivalent nonnested expressions.

• Aliases are no longer automatically created for Parameter blocks while reading in Real-Time Workshop files.
• You cannot change the contents of a "Default" record after it has been created. In the previous TLC, you could change a "Default" record and see the change in all the records that inherited from that default record.
• %codeblock and %endcodeblock constructs are no longer supported.
• %defines & macro constructs are no longer supported.
• Use of line continuation characters (... and \) are not allowed inside of strings. Also, to place a double quote (") character inside a string, you must use \". Previously, TLC allowed you to do """ to get a double quote in a string.
• Semantics have been formalized to %include files in different contexts (e.g., from generated files inside of %with blocks, etc.) %include statements are now treated as if the were read in from the global scope.
• The previous TLC had the ability to split function definitions (and other directives) across include file boundaries (e.g., you could start a %function in one file and %include a file that had the %endfunction). This no longer works.
• Nested functions are no longer allowed. For example,

• %function foo ()
    %function bar ()
    %endfunction
  %endfunction
  

• Recursive records are no longer allowed. For example,

• Record1     {
    Val 2
    RefRecord2
  }
  Record2     {
    Val3
    RefRecord1
  }
  

• Record declaration syntax has changed. The following code code fragments illustrate the differences between declaring a record recVar in previous versions of TLC and the current release.
• Previous versions:

• %assign recVarAlias = recVar { ...
      field1  value1 ...
      field2  value2 ...
      ...
      fieldN  valueN ...
  }
  

• Current version:

• %createrecord recVar { ...
      field1  value1 ...
      field2  value2 ...
      ...
      fieldN  valueN ...
  }
  

• See Records for further information.

• Semantics of the EXISTS function have changed. In the previous release of TLC, EXISTS(var) would check if the variable represented by the string value in var existed. In the current release of TLC, EXISTS(var) checks to see if var exists or not.

• To emulate the behavior of EXISTS in the previous release, replace

  • EXISTS(var) 
    

with

• EXISTS("%<var>")
  

New Features and Compatibility Issues in Versions 4.0, 4.1, and 5.0

Where to Go from Here