Read-write configuration data
sebastian.huber at embedded-brains.de
Fri Nov 9 09:06:22 UTC 2012
On 11/08/2012 10:59 PM, Claus, Ric wrote:
>>> 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.
How do you do this? Do you read the values of the configuration structures and
store them somehow? Later you use the stored values and create a new
configuration from these values for a specific application? What happens if
the configuration structure layout changes?
I think we should record this requirement somewhere. I was not aware that such
a use case exists.
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