Re: [PATCH] score: Compact objects class indices

On 22/05/2019 15:55, Joel Sherrill wrote: On Wed, May 22, 2019 at 8:40 AM Sebastian Huber > wrote: On 22/05/2019 15:23, Joel Sherrill wrote: > I'm OK with this. > > Is the statement that the API and class numbers are not > guaran

Re: [PATCH] score: Compact objects class indices

On Wed, May 22, 2019 at 8:40 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 22/05/2019 15:23, Joel Sherrill wrote: > > I'm OK with this. > > > > Is the statement that the API and class numbers are not > > guaranteed to be held constant across releases something > > that shoul

Re: [PATCH] score: Compact objects class indices

On 22/05/2019 15:23, Joel Sherrill wrote: I'm OK with this. Is the statement that the API and class numbers are not guaranteed to be held constant across releases something that should be explicitly in a comment or requirement? The question is how can an application get one of the class number

Re: [PATCH] score: Compact objects class indices

I'm OK with this. Is the statement that the API and class numbers are not guaranteed to be held constant across releases something that should be explicitly in a comment or requirement? On Wed, May 22, 2019 at 12:52 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > --- > cpukit/

[PATCH] score: Compact objects class indices

--- cpukit/include/rtems/score/objectdata.h | 48 +++-- 1 file changed, 28 insertions(+), 20 deletions(-) diff --git a/cpukit/include/rtems/score/objectdata.h b/cpukit/include/rtems/score/objectdata.h index ce6e3c63a4..a33f9d497f 100644 --- a/cpukit/include/rtems/scor