Backwards compatibility of commands for developer use

Question

question

Shinya O asked Sep 15, '23 Jason Lightfoot edited Sep 25, '23

Backwards compatibility of commands for developer use

Hi,

The following article mentions applicationcommand() as follows:

The command applicationcommand() is designed to be used and maintained by FlexSim developers for FlexSim developers. The various options that are available are subject to change in future versions.

https://answers.flexsim.com/questions/29913/how-to-know-all-the-command-that-applicationcomman.html

Will this also change in the future for all commands described as "For developer use" in the command reference? Isn't there backward compatibility?

https://docs.flexsim.com/en/23.0/Reference/CodingInFlexSim/CommandReference/Commands.html

Thanks in advance.

Software Version:

FlexSim 23.0.11

commands backward compatibility

· 1

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Joerg Vogel commented · Sep 15, 2023 at 05:51 AM

Typically there are a lot of deprecated commands. They exist and they still work. There are other special functions to call "function_s" which are deeper connected to FlexSim. Such calls are replaced by other structures like FlexScript Class API "create" calls.

But what you read there is a typical statement of every high progressive software tool. You can be certain, that a new version replaces tools by other methods. For example you will learn, that FlexSim changes their statistical tools roughly estimated all five years.

0 ·

Answer 1 · 2023-09-25T17:06:11Z

Jason Lightfoot answered Sep 25, '23 Jason Lightfoot edited Sep 25, '23

Mostly commands, methods and functions in the user space will be backward compatible. Sometimes you'll see in the release notes that something changes the behavior from previous versions with a note on backward compatibility.

As various posts on the forum already indicate - developer tools may change in the future so you should not use them extensively through out the model as a future change would mean potentially a lot of work updating the model. Instead - try to centralize such calls in user commands or object process flow custom code activities, then if something breaks you only need update it in one place.

· 1

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Matthew Gillespie ♦♦ commented · Sep 25, 2023 at 05:32 PM

Everything in the FlexScript API is fully backwards compatible.

Everything in the Command Reference, except those marked as developer only, is fully backwards compatible.

Functions called using the applicationcommand() or function_s() commands are not guaranteed to be backwards compatible and should not be used if you're worried about it not working in future versions.

1 ·

question