Release 0.9.44

0.9.44

• New configuration item regex_attribute_name for the
  naming_functions rule. This can be used to enforce naming for
  class attributes and the associated getters and setters.

Release 0.9.43

0.9.43

• Fix parsing error surrounding function names (only in classes may
  you use a dotted name). When such a function appeared outside a
  class the tools would either incorrectly accept this name or crash.

• Fix hanging tools when an internal compiler error was raised.

• Fix parser error for enumeration values with no parameters using
  brackets.

• Fix tool crash when --debug-dump-tree was specified without
  --single. This is now clear in the error message.

• Add new configuration directive ignore_dir. This works just like
  exclude_dir but does not raise an error if the directory doesn't
  exist.

• Add new configuration option newline_style. By default MISS_HIT
  will just use the native line endings, but by setting
  newline_style to lf, crlf, or cr you can force it to use
  platform-specific newlines. You can also use native to restore the
  default behaviour.

Release 0.9.42

0.9.42

• Fix issue with MATLAB functions embedded in Simulink. Usually people
  left the default name (i.e. fcn) which caused many duplicate items
  to appear in the mh_trace output. Now embedded functions use the
  name of the subsystem (i.e. what you'd see in Simulink as the name).

Release 0.9.41

0.9.41

• Fix parsing bug for argument and property validation blocks. The
  list of validation functions may be empty, previously the MISS_HIT
  parser complained about non-empty lists.

Release 0.9.40

0.9.40

• Fix tool crash when encountering a Simulink area annotation with no
  text. These annotations are now properly supported and you can even
  add tracing text to them.

Release 0.9.39

0.9.39

• Add another method of tracing Simulink models via block
  properties.

• The top-level system of a Simulink Library (but not Model) no longer
  appears in the tracing output, as there is no way to access or
  manipulate this in the Simulink user interface.

• Add new option --untagged-blocks-inherit-tags for mh_trace which
  cases any untagged system to inherit any tags from its parent. Once
  new tags are encountered this breaks the inheritence chain. Note
  that embedded MATLAB blocks are unaffected by this option.

Release 0.9.38

0.9.38

• Fix issue where a Simulink model with self-contained links would not
  parse the referenced systems. Only the top-level system would be
  parsed and references were never followed.

• Fix issue where a Simulink model with referenced stateflow would not
  parse the referenced machines and charts.

• Fix issue in mh_trace where sometimes LOBSTER tags could be
  generated which contained spaces.

• Support multi-line and HTML annotations in Simulink for mh_trace
  annotations.

Release 0.9.37

0.9.37

• Rework mh_trace and its output format. It now generates LOBSTER
  traces. See https://github.com/bmw-software-engineering/lobster for
  more information, including a description of the interchange
  format. The old output format is no longer supported now that there
  is a good standard.

• Add support for Simulink tracing in mh_trace. You can add
  annotations to any block starting with the text lobster-trace:
  followed by a list of requirement tags. For example lobster-trace: foo.my_req.

• Remove mh_trace commandline flag --json and replace it with
  --out-imp and --out-act. The default filename produced is now
  mh_imp_trace.lobster and mh_act_trace.lobster.

• Remove mh_trace commandline flag --by-tag. You can use a tool
  like LOBSTER to recover this information.

• Add mh_trace commandline flag --only-tagged-blocks. This filters
  out all Simulink blocks that do not contain at least one tag.

• Fix a bug in mh_trace where precisely duplicated package +
  function names result in only one tracable item. Now there are two,
  and a tool like LOBSTER will complain.

Release 0.9.36

0.9.36

• Fixed minor issue where mh_trace was not made available as a
  command-line tool when installing the PyPI package miss_hit.

Release 0.9.35

0.9.35

• You can now specify more precise Octave and MATLAB versions. This
  change is massive, and likely to have subtle bugs. You can now write
  octave: "4.4" or matlab: "2020b" in your config files; or specify
  --octave=4.4 or --matlab=2020b from the command-line. There is
  also a special latest version for both Octave and MATLAB, which is
  an alias for the latest supported version.

  This is also the first change that introduces backwards
  incompatibility, specifically:

  • The command-line option --octave no longer works. You need to
    specify --octave=latest to get the same behaviour.
  • The config setting octave: true still works, but is
    deprecated. It means the same thing as octave: "latest".
  • The config setting octave: false doesn't make sense anymore (and
    never really did), so it now raises an error.

  As always note that for MATLAB, support should be fairly good and
  accurate. For Octave many things are missing (such as the end_X
  set of keywords). I do plan to improve the situation, but please
  create tickets for things you need sooner.

• Several tools that generate messages (mh_style, mh_metric, and
  mh_lint) will now add the originating check id in the message. For
  example:

  In test.m, line 4
  | false = 0.01; % bad
  | ^^^^^ check (medium): redefining this builtin is very naughty [builtin_shadow]
  

  This should make it much easier to disable rules if you don't like
  to read the manual.

• MISS_HIT now recognises and processes Octave test .tst files
  (along with .m and .slx files). The Octave test annotation
  language (comments starting with %!) is ignored by MH Style for
  now. Thank you to Alois Spitzbart for the idea.