Re: silly ravenscar question

[Simon Wright <simon@pushface.org>]

Brad Moore <brad.moore@shaw.ca> writes:

> You might be thinking of the restriction, No_Implicit_Heap_Allocations
> which is part of the Ravenscar Profile. That restricts the runtime
> from making allocations from the heap, but it does not restrict
> application code from using the heap to allocate objecs.

From a hobbyist point of view, the Ravenscar approach to _tasking_ makes
a lot of sense, because full Ada tasking is very hairy (the restricted
tasking in GNAT's Ravenscar is hairy enough).

But some of the other restrictions, like this one, are less appropriate
outside the critical area.

OK, so far the only user-visible effect I see is in packages like
Interfaces.C.Strings, where it's obvious to you and me that
New_Char_Array and New_String are going to allocate memory, but
No_Implicit_Heap_Allocations prevents 'new' (I used FreeRTOS's memory
management routines instead), and in Containers, where you're restricted
to the Bounded versions (no great problem there).