Re: API deprecation

2015-03-08 Thread Joel Sherrill
On March 8, 2015 8:49:39 PM CDT, Chris Johns wrote: >On 9/03/2015 8:46 am, Joel Sherrill wrote: >> >> We could turn these features off by default and require a special >configure argument to enable them. >> > >Do you mean turn of the depreciated code or the warning ? Yes. You should get a linke

Re: API deprecation

2015-03-08 Thread Chris Johns
On 9/03/2015 8:46 am, Joel Sherrill wrote: We could turn these features off by default and require a special configure argument to enable them. Do you mean turn of the depreciated code or the warning ? FYI rtems_clock_get() should also be deprecated. Probably need a ticket for it, taj vs

Re: API deprecation

2015-03-08 Thread Joel Sherrill
On March 8, 2015 4:43:00 PM CDT, Chris Johns wrote: >On 5/03/2015 8:26 am, Gedare Bloom wrote: >> We have ticket #2265 requesting to deprecate notepads. It was also >> suggested we deprecate per-task variables. > >Task variables should be removed. There are suitable SMP safe solutions > >availab

Re: API deprecation

2015-03-08 Thread Chris Johns
On 5/03/2015 8:26 am, Gedare Bloom wrote: We have ticket #2265 requesting to deprecate notepads. It was also suggested we deprecate per-task variables. Task variables should be removed. There are suitable SMP safe solutions available. Having an API that is only supported in uni-processor conf

API deprecation

2015-03-04 Thread Gedare Bloom
We have ticket #2265 requesting to deprecate notepads. It was also suggested we deprecate per-task variables. Do we have an established procedure for how to deprecate an API? Does anyone have any objections? Gedare ___ devel mailing list devel@rtems.org