Read-write configuration data
claus at slac.stanford.edu
Thu Nov 8 21:59:08 UTC 2012
On Nov 8, 2012, at 1:16 PM, Sebastian Huber wrote:
> On 08/11/12 20:00, Claus, Ric wrote:
>> So long as what you mean by read-only can be overridden in a controlled way when needed, I have no objection.
> They are statically initialized global structures and usually
> initialized via confdefs.h.
Okay, if this is what you're doing, fine. From your statements it wasn't clear whether you were planning to rework this.
>> If, however, you are intending to move toward compiled-in literals, then I am not in favor. Ideally, all configuration constants would reside in some sort of database object, the contents of which could easily be recorded at run time. This would be useful for gaining confidence in the ability to correctly reproduce past situations.
> What do you mean with "recorded at run time" and "reproduce past
Some applications need to be able to record their configuration (including that of RTEMS) at run time so that at some later date when a test needs to be repeated, there is some hope of being able to reproduce it by reestablishing that configuration. Relying on discipline to commit files, record tags, etc. invites mistakes.
I'm not sure that this is any clearer than what I first wrote.
> Sebastian Huber, embedded brains GmbH
> Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
> Phone : +49 89 18 90 80 79-6
> Fax : +49 89 18 90 80 79-9
> E-Mail : sebastian.huber at embedded-brains.de
> PGP : Public key available on request.
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the devel