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@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users