Le 01/07/2020 à 13:47, Stéphane Mottelet a écrit :
Right, sorry for my previous message.
But, at the user level there are very few use cases: the clear
overload is only useful if some mlist fields contain some pointers to
allocated data. For example sparse LU factors or Java objects.
The auto-clearing of the Java side of Java objects is already
implemented (and it's documented).
I am wondering if a similar native auto-clearing could be implemented
for xml and hdf5 objects.
I guess that usingclear before h5close() or xmlDelete() could make
memory leaking.
Samuel
_______________________________________________
users mailing list
[email protected]
http://lists.scilab.org/mailman/listinfo/users
