Menu

#986 The --output option does not work as shown in course material

Version 4.0 RC1
new
None
none
core
blocker
defect
2016-08-10
2016-08-10
No

The --output option fails on the .glm extension, and when .txt or .gld are used it creates files that cannot be loaded. The file format used is the Version 1 GLM format and many newer features result in GLM syntax that is not valid. The saveall() function needs to put #ifdefs around anything that isn't fully supported by the loader.

Discussion

  • David P. Chassin

    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1 @@
    -The --output option fails on the .glm extension, and when .txt or .gld are used it creates files that cannot be loaded.  The file format used is the Version 1 GLM format and many newer features result in GLM syntax that is not valid.  The saveall() function needs to put #ifdefs around anything that isn't fully supported by the loader.
    +The `--output` option fails on the `.glm` extension, and when `.txt` or `.gld` are used it creates files that cannot be loaded.  The file format used is the Version 1 GLM format and many newer features result in GLM syntax that is not valid.  The `saveall()` function needs to put `#ifdef`s around anything that isn't fully supported by the loader.
    
     
  • David P. Chassin

    Note also that the output routines do not output all model elements. In particular, filter, schedules, user-defined globals, and runtime code is not stored in the output file.

     
  • David P. Chassin

    One highly desirable feature in the GLM output to provide #ifdef INCLUDE_XYZ / #endif around each non-essential output block, e.g., class definitions, non-default globals.

     
  • David P. Chassin

    There should be validation tests for GLM output, i.e., load a model with asserts, output the model and then run a separate test that inputs the model with the simple GLM code

    #include "output_model.glm"