Hello Sebastian,
On Thursday 23 of July 2015 13:31:23 Sebastian Huber wrote:
> Hello Pavel,
>
> thanks for your comments.
>
> On 23/07/15 12:40, Pavel Pisa wrote:
> > Hello Sebastian,
...
> > I fully understand your motivation and for small footprint system
> > the direct pointers use is most effi
On 23/07/15 13:51, Joel Sherrill wrote:
On 7/23/2015 6:36 AM, Sebastian Huber wrote:
On 23/07/15 12:29, Chris Johns wrote:
I feel this needs to be a real API not a pseudo-internal API. Making
this an API means the project agrees to support the API, it has tests
and we have to make sure it i
On 7/23/2015 6:36 AM, Sebastian Huber wrote:
On 23/07/15 12:29, Chris Johns wrote:
I feel this needs to be a real API not a pseudo-internal API. Making
this an API means the project agrees to support the API, it has tests
and we have to make sure it is working for a release. Oh and it has
docu
Hello Pavel,
thanks for your comments.
On 23/07/15 12:40, Pavel Pisa wrote:
Hello Sebastian,
the first big thanks for RTEMS architectural updates.
On Thursday 23 of July 2015 11:16:03 Sebastian Huber wrote:
The Classic RTEMS and POSIX APIs have at least three weaknesses.
* Dynamic memory (t
On 23/07/15 12:29, Chris Johns wrote:
I feel this needs to be a real API not a pseudo-internal API. Making
this an API means the project agrees to support the API, it has tests
and we have to make sure it is working for a release. Oh and it has
documentation.
For an API I suggest to use C11/C++
Hello Sebastian,
the first big thanks for RTEMS architectural updates.
On Thursday 23 of July 2015 11:16:03 Sebastian Huber wrote:
> The Classic RTEMS and POSIX APIs have at least three weaknesses.
>
> * Dynamic memory (the workspace) is used to allocate object pools. This
>requires a complex
Spam detection software, running on the system "corb.contemporary.net.au",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
The administrator of that system for deta
The Classic RTEMS and POSIX APIs have at least three weaknesses.
* Dynamic memory (the workspace) is used to allocate object pools. This
requires a complex configuration with heavy use of the C pre-processor.
* Objects are created via function calls which return an object identifier.
The obj
