Read-write configuration data

[Joel Sherrill]

IMHO if they are generated by confdefs.h, then they should be able to be read only. I have worked in this area on and off for years to do clean up and appreciate you doing this. Historically, there was just a long history of not being const and if we have cleaned that up, let's switch.

--joel

Sebastian Huber <sebastian.huber at embedded-brains.de> wrote:

>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