Help with memory allocation/deallocation and matrix/vector libraries for scientific computations
No doubt that ADA since its very beginning got almost everything right as it regards syntax and semantics. If I start listing things I adore about this Language, it will be boring, so I would prefer to discuss with you a few things that might and I repeat “might” need improvement.
Deallocation could be made simpler and easier to remember without hurting overall functionality.
procedure Free is new Ada.Unchecked_Deallocation(…)
is probably too cumbersome. Perhaps Storage pool is the most elegant alternative. Are there any more modern approaches? I apologise for my ignorance here but the standard keeps changing and documentation with examples around the web is not that easy to find for ADA, free books are quite old.
2. Matrix/Vector libraries
Applications of Real_Arrays are limited due to static allocations by default, no easy/dynamic stack storage sizing, and temporary objects when overloading operators. Are any other library alternatives ?
Any plans from ADA headquarters for native support of Matrix/Vector operations similar to Fortran without temporaries and Fortran efficiency? Same for complex numbers?
Thank you all in advance.
12 posts - 4 participants