CVS difference for ai05s/ai05-0189-1.txt

Differences between 1.1 and version 1.2
Log of other versions for file ai05s/ai05-0189-1.txt

--- ai05s/ai05-0189-1.txt	2009/11/04 01:50:45	1.1
+++ ai05s/ai05-0189-1.txt	2009/11/04 06:26:38	1.2
@@ -58,4 +58,37 @@
 
 !appendix
 
+From: Tucker Taft
+Sent: Friday, June 12, 2009  6:23 AM
+
+This is an official request from Ada Switzerland for a restriction that
+disallows allocation after library-unit elaboration is complete.
+
+[Editor's note: Not sure when Tucker becaome Swiss! I presume he meant to
+say that he is relaying an official request from Ada Switzerland, or some
+such thing.]
+
+****************************************************************
+
+From: Jean-Pierre Rosen
+Sent: Friday, June 12, 2009  12:05 PM
+
+No_Local_Allocator seems to come close...
+
+****************************************************************
+
+From: Tucker Taft
+Sent: Friday, June 12, 2009  3:44 PM
+
+True, but it is too limiting.  It means that you can't use allocators in
+subprograms, even if they are called only during library-unit elaboration.
+That pretty much defeats any kind of abstraction.
+
+Many embedded systems have the model of allowing dynamic allocation during
+start up, but not thereafter. Ada really ought to support that. What I would
+imagine is a restriction that disallows use of a default storage pool after
+elaboration is complete, while allowing user-defined storage pools to check
+in the Allocate procedure against some global flag that indicates whether
+library-level elaboration is complete.
+
 ****************************************************************

Questions? Ask the ACAA Technical Agent