The textual SCADE language is what we often refer too as LUSTRE, but as explained below, there are differences between LUSTRE and textual SCADE and the correct name is thus SCADE textual language. The actual textual SCADE language initially derives from the so-called V3+ version of LUSTRE, an industrial version that incorporates some extensions (like type refinements) with respect to LUSTRE V3. On the academic side, important extensions were added, to cope with a project of silicon compiling (in particular array types), and which gave birth to 2 other versions of the compiler: LUSTRE-V4 and LUSTRE-V5 (which are slightly different from the actual industrial version). The textual SCADE language is used to save SCADE models. Therefore SCADE “.saofd” files contain the SCADE textual definition of their respective blocks (nodes, constants/types/global variables definitions). SCADE Editor enables to define a node directly with the SCADE textual language (textual nodes), which is handy for som
The textual SCADE language is what we often refer too as LUSTRE, but as explained below, there are differences between LUSTRE and textual SCADE and the correct name is thus SCADE textual language. The actual textual SCADE language initially derives from the so-called V3+ version of LUSTRE, an industrial version that incorporates some extensions (like type refinements) with respect to LUSTRE V3. On the academic side, important extensions were added, to cope with a project of silicon compiling (in particular array types), and which gave birth to 2 other versions of the compiler: LUSTRE-V4 and LUSTRE-V5 (which are slightly different from the actual industrial version). The textual SCADE language is used to save SCADE models. Therefore SCADE “.saofd” files contain the SCADE textual definition of their respective blocks (nodes, constants/types/global variables definitions). SCADE Editor enables to define a node directly with the SCADE textual language (textual nodes), which is handy for som