Read-write configuration data

[Claus, Ric]

So long as what you mean by read-only can be overridden in a controlled way when needed, I have no objection.  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.

Ric

________________________________________
From: rtems-devel-bounces at rtems.org [rtems-devel-bounces at rtems.org] On Behalf Of Sebastian Huber [sebastian.huber at embedded-brains.de]
Sent: Thursday, November 08, 2012 6:59 AM
To: RTEMS
Subject: Read-write configuration data

Hello,

a lot of the RTEMS configuration is read-write data.

Configuration_POSIX_API
Configuration_RTEMS_API
Device_drivers
_POSIX_Threads_Initialize_user_threads_p
rtems_fs_init_helper
rtems_libio_init_helper
rtems_libio_number_iops
rtems_libio_supp_helper
rtems_malloc_dirty_helper
RTEMS_Malloc_Heap
rtems_malloc_statistics_helpers
rtems_maximum_priority
rtems_minimum_stack_size
_RTEMS_tasks_Initialize_user_tasks_p
rtems_telnetd_maximum_ptys
_Scheduler

Are there objections to make them read-only?

--
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.

_______________________________________________
rtems-devel mailing list
rtems-devel at rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel