Hi, just my two cents: Would an additional call 'rtems_shell_init_once_commandset()' make sense, where the user can specify, which comamnds are available?
I agree that changing the functionality of an existing call is not a good idea. Thomas. ----- Ursprüngliche Mail ----- Von: "Chris Johns" <chr...@rtems.org> An: "Development" <devel@rtems.org> Gesendet: Freitag, 16. März 2018 08:01:14 Betreff: RTEMS monitor commands and the shell Hi, The monitor commands are registered automatically in `rtems_shell_init_once()` which means an application has no control over these being present, the command mix and naming, for example there is a `config` command in the monitor. I am not sure what to do, if it is removed some applications may break assuming these commands are present. A way to disable the command using shellconfig.h would be nice. Suggestions? Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel -- -- -------------------------------------------- embedded brains GmbH Thomas Doerfler Dornierstr. 4 D-82178 Puchheim Germany email: thomas.doerf...@embedded-brains.de Phone: +49-89-18 94 741-12 Fax: +49-89-18 94 741-09 PGP: Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
