<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Le 09/04/2021 à 18:08, Antoine
Monmayrant a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:37d06d48-5793-9131-a6a4-db628cf5c7aa@laas.fr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><br>
</p>
<div class="moz-cite-prefix">On 09/04/2021 17:57, Samuel Gougeon
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f411d60c-4799-1c5f-37ca-8945111803af@free.fr">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<p><font face="Arial">Dear all,</font></p>
<p>I am wondering about precedence rules when a user's defined
builtin (possibly from an ATOMS external module) has the same
name than a native Scilab builtin function.<br>
The case appeared (and maybe still) when using the scicv
external module, that redefined a write() function that
already exists in Scilab.<br>
<br>
Does anyone know how such conflicts are managed by Scilab?<br>
</p>
</blockquote>
<p>Poorly or not at all according to my own painful experience
with grocer and scicv that caused weird behaviours by
overloading existing functions...</p>
</blockquote>
<p>Doesn't Grocer use only macros, not a single builtin function?<br>
My question is only about hard-coded (so called builtin or
"primitive") functions.<br>
<br>
</p>
</body>
</html>