Opened 9 years ago

Last modified 3 years ago

#3572 accepted defect

Clarifications in the Compiler Flag Documentation

Reported by: Francesco Casella Owned by: Lennart Ochel
Priority: high Milestone:
Component: *unknown* Version:
Keywords: Cc: andrea.bartolini@…

Description

The web page https://openmodelica.org/doc/OpenModelicaUsersGuide/latest/omchelptext.html lists all compiler flags, and is automatically generated from omc help info.

The situation has improved dramatically once #2913 was addressed. However, there are four things that still need to be fixed.

  1. The documentation gives -d and --debug as debug flags. However, in the page there are still three references to +d, which are very confusing because it is not clear whether that is a separate flag with different effects or not. Please always use the same notation -d everywhere. You may also mention in the documentation that the +d notation is deprecated but can still be found in existing code
  1. The documentation https://openmodelica.org/doc/OpenModelicaUsersGuide/latest/omchelptext.html#omcflag-debug-section explains how to set up the -d flag. However, there are no examples. I would suggest to add one or two, and at least one where multiple flags are set and some are reset, for better clarity.
  1. The documentation of --preOptModules, --initOptModules and --postOptModules does not contain any example, so it is not clear how one can actually set the options that are listed there. I would suggest to add a couple of examples from which it is clear what the syntax is.
  1. The new flags introduced in https://github.com/OpenModelica/OMCompiler/pull/282 are not documented at all, please add the documentation of --forceRecommendedOrdering and also add the documentation about += and -= to --preOptModules, and --postOptModules. BTW, can this also be used with --initOptModules, or should a special section dedicated to flags used in initOptModules be also introduced in the documentation?

Change History (13)

comment:1 by Lennart Ochel, 9 years ago

Status: newaccepted

comment:2 by Lennart Ochel, 9 years ago

I will improve the documentation a bit.

Please note that the documentation already contains all the default values. E.g. --preOptModules is described here including the default value and all valid options.

The flag --forceRecommendedOrdering is renamed into --defaultOptModulesOrdering and briefly described here.

Moreover I suggest to remove a bunch of flags, to make the usage of omc more consistent and less complicated (see #3568#comment:9).

in reply to:  2 comment:3 by Francesco Casella, 9 years ago

Replying to lochel:

Please note that the documentation already contains all the default values. E.g. --preOptModules is described here including the default value and all valid options.

This is true, but it is not clear how you apply the string list to the flag - do you need an equality sign? Can you have spaces beween the flag and the string? Has the string to be quoted? A small example would suffice, following the old tradion of man pages.

comment:4 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.5

Milestone pushed to 1.9.5

comment:5 by Martin Sjölund, 9 years ago

Milestone: 1.9.51.10.0

Milestone renamed

comment:6 by Martin Sjölund, 8 years ago

Milestone: 1.10.01.11.0

Ticket retargeted after milestone closed

comment:7 by Martin Sjölund, 8 years ago

Milestone: 1.11.01.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:8 by Francesco Casella, 7 years ago

Milestone: 1.12.01.13.0

Milestone moved to 1.13.0 due to 1.12.0 already being released.

comment:9 by Francesco Casella, 6 years ago

Milestone: 1.13.01.14.0

Rescheduled to 1.14.0 after 1.13.0 releasee

comment:10 by Francesco Casella, 5 years ago

Milestone: 1.14.01.16.0

Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0

comment:11 by Francesco Casella, 4 years ago

Milestone: 1.16.01.17.0

Retargeted to 1.17.0 after 1.16.0 release

comment:12 by Francesco Casella, 4 years ago

Milestone: 1.17.01.18.0

Retargeted to 1.18.0 because of 1.17.0 timed release.

comment:13 by Francesco Casella, 3 years ago

Milestone: 1.18.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.