Simulink Truth Table Action Language Whitespace

Simulink Truth Table Action Language Whitespace:

I've found that the action language for truth tables in Simulink do not support space characters before and after the equals sign. This was discovered in R2020b.

For example, the statement below will not compile:

x = true;

The statement below will compile:

x=true;

The error message that occurs when using the first statement does not indicate the problem is with whitespace. Instead, it implies that I used an '=' when I meant '==' or vice-versa, which wasn't the problem.

This was very difficult for me to track down the problem. I think a future update should either support spaces in the action language, or update the error handler so it mentions white space as a potential cause of the compile error in the error message. I also wanted to post this in case someone else runs into the same problem; perhaps they can search and find this.

More details when this was encountered:

• Truth Table used within Stateflow Chart with Matlab action language
• Data object 'x' existed in Chart context with 'boolean' data type and 'local' context
• Conditions handled similarly (boolean data objects local to chart). Whitespace was used in conditional statements in the Truth Table with no error.
• Truth Table code interface set to generate 'inlined' within Chart code.

[Roman]

Hi Paul, I followed your steps and cannot reproduce this in 20b, see the attached picture. What am I missing?

[Paul Rancuret]

Roman,

Actually I had opened a ticket about this back in March 2023 with the following reference in the emails:

ref:_00Di0Ha1u._5003q1aB2lM:ref

Unfortunately I was unable to replicate the behavior I was seeing in a share-able model, so I never was able to figure out exactly what was happening. It might have been some different problem with the particular model we were using. I had recommended that we close the ticket back then, and I haven't run into the problem anymore. I think at the time I mentioned it might make sense to remove this post, but I wasn't sure how to do so. Sorry for the confusion.

Answer 1

[Teresa Hubscher-Younger]

Thanks! I will report this to documentation, so that they can cover what you discovered there.

[Paul Rancuret]

Teresa,

Actually I had opened a ticket about this back in March 2023 with the following reference in the emails:

ref:_00Di0Ha1u._5003q1aB2lM:ref

Unfortunately I was unable to replicate the behavior I was seeing in a share-able model, so I never was able to figure out exactly what was happening. It might have been some different problem with the particular model we were using. I had recommended that we close the ticket back then, and I haven't run into the problem anymore. I think at the time I mentioned it might make sense to remove this post, but I wasn't sure how to do so. Sorry for the confusion.