You may find hints for missing subroutines in advance in the Analyser Report List if Analyser Preference "Check for inappropriate subroutine CALLs and missing call targets" is enabled. Unavailable subroutines the exported diagram depends on will be reported without aborting the export process (the definitions will simply be missing in the resulting file(s)).
#STRUCTORIZER DOWNLOAD HOW TO#
In this case Structorizer wouldn't know how to translate your code into any other language, though.Įxport Option " Involve called subroutines" is to enrich the code for the selected diagram with the routine definitions for all subroutines referred to by contained CALL elements and all includable diagrams referenced in the include list - if the corresponding diagrams are reachable via the Arranger. It is recommended to use this option if you explicitly write target code in Structorizer elements. The Export Option " No conversion of the expression/instruction contents" allows you to perform a kind of raw export with mere control structure conversion and mostly suppressed translation of the element contents.
#STRUCTORIZER DOWNLOAD MANUAL#
Usually "TODO" comments inserted in the generated code will guide you through the manual post-processing work. Some algorithmic construct may not directly be translatable such that the generators must try their best to compose something closely equivalent. You will have to check for wrong, missing or mis-placed declarations and must accomplish or correct them manually. You should be aware, of course, that the generated program files may usually not immediately be compilable or executable in the target language but require some manual post-processing because the generators will have to do a lot of mere guesswork: Though Structorizer tries hard to derive static type information from assignments or implicit declarations, the types of many of the used variables will not be known such that the generators will hardly be able to produce complete declaration lists for languages that require strict declaration. In the Export Preferences you may select your most frequently used (favourite) target language in order to accelerate the export via key combination Ctrl+Shift+X: If the group had to be partinioned then you will get the following information: Group export allows to generate libraries consisting of several public routines, which are not necessarily referencing each other. (If this menu item happens to be missing in a version ≥ 3.30-11 then it is likely to be due to an export/import suppression mode, see Export Configuration note.) Having selected a group or a single diagram in the list, you may start the export via menu item " Export diagram/group ›" and the name of the language you want to export to. Group ExportĪnother way to export source code from a diagram or even an entire arrangement group is to use the context menu of the Arranger Index. Note the general export configuration opportunities and in particular that some of the languages (actually Basic, ARM, and LaTeX/Algorithm so far) may have additional generator-specific options.
You may also start the export from the Code Preview via the context menu. The currently supported programming or script languages are the following ones (where StruktTeX and LaTeX/Algorithm are not actually a programming languages but related to L AT EX add-ons providing embeddable NSD drawings or pseudocode illustrations, see Export Preferences for examples of the latter): (In case these menu entries happen to be missing, see Export Configuration note.) To export the current diagram in the work area as code, go to the menu and select " File › Export › Code ›" and the name of the language you want to export to. For being able to do this, the generators must be fed the necessary information about the syntax you are using in your diagrams. Whereas a "C" export will result in the code:Īs you can notice, the words " pour" and " à" have been eliminated or replaced with whatever the exported code requires. If you then do a "Pascal" export, the generated code will be: ":Īll the words you filled in there will be filtered out and replaced by the respective target language keywords.įor example, if your diagram contains a FOR loop and you are writing french diagrams, you may have something like this: You can find them via the menu " Preferences › Parser.
First of all, if you want to use the code generators, you should make sure to have filled in the parser preferences appropriately.
0 kommentar(er)
