<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 21/12/2018 à 19:40, Samuel Gougeon a
écrit :<br>
</div>
<blockquote cite="mid:1451fbe9-c1c2-b5df-47c4-6364343dcf5a@free.fr"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Hello Clément,<br>
<br>
Le 21/12/2018 à 14:19, Clément David a écrit :<br>
</div>
<blockquote
cite="mid:AM6PR0502MB370207916FBD937975C04D77B0B80@AM6PR0502MB3702.eurprd05.prod.outlook.com"
type="cite">
<pre wrap="">Dear devs,
After CNES presentation on Scilab Conference 2018, I would like to propose a solution to the mandatory use of `jremove`. The point is : some Scilab functionalities based on mlist overloading are implemented in C/C++ with manual memory management or in Java with garbage collected memory. How to clean-up the associated resources on Scilab mlist deletion ?
I wrote a SEP about adding a "delete" overloading to describe that [1], please comment and give feedbacks !
[1]: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://wiki.scilab.org/SEP%20add%20a%20%25foo_delete%20overloading">https://wiki.scilab.org/SEP%20add%20a%20%25foo_delete%20overloading</a>
Thanks,</pre>
</blockquote>
<br>
<br>
Thanks for this proposal. I have a couple of questions about it:<br>
In the example that you provide, %foo_delete() is aimed to be
called when calling clear().<br>
Using clear looks indeed the most handy and simple. It is the main
most known deleting function.<br>
<br>
AFAIK The naming convention for the overload of any primitive is
%<type>_builtinName.<br>
So, why naming/calling the overload %foo_delete() instead of
%foo_clear()?<br>
<br>
Are you sure that the bug 10258 is related?<br>
I would rather say that the <a moz-do-not-send="true"
href="http://bugzilla.scilab.org/show_bug.cgi?id=10277">bug
10277</a> and the <a moz-do-not-send="true"
href="http://bugzilla.scilab.org/show_bug.cgi?id=13398">bug
13398</a> are so.<br>
By the way, 10258's author actually proposes to call %foo_clear().<br>
</blockquote>
<br>
Sorry: ..so, 10277's author...
</body>
</html>