[Scilab-users] Precedence rules for concurrent native and external builtin homonymous functions?

[Stéphane Mottelet]

Samuel, I think the problem is about gateways not user macros right ?

What I experienced is that the new gateways have precedence over the 
previously linked gateways with the same name.

Hence, there is no conflict is the API is respected...

S.

Le 09/04/2021 à 17:57, Samuel Gougeon a écrit :
>
> Dear all,
>
> 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.
> The case appeared (and maybe still) when using the scicv external 
> module, that redefined a write() function that already exists in Scilab.
>
> Does anyone know how such conflicts are managed by Scilab?
> Thanks
>
> Samuel
>
>
> _______________________________________________
> users mailing list
> users at lists.scilab.org
> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users

-- 
Stéphane Mottelet
Ingénieur de recherche
EA 4297 Transformations Intégrées de la Matière Renouvelable
Département Génie des Procédés Industriels
Sorbonne Universités - Université de Technologie de Compiègne
CS 60319, 60203 Compiègne cedex
Tel : +33(0)344234688
http://www.utc.fr/~mottelet

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20210409/730276a9/attachment.htm>