Le 12/04/2019 à 18:40, Samuel Gougeon a écrit :
.../...
Maybe we can include functions in un/protect feature but what to do
with funcprot ?
I think it will be difficult to keep both and that will be puzzling
for users.
Samuel: clearly, if some "class protection" is implemented and enabled
in addition to some object protection, funcprot() would have to be
deprecated and removed.
Now, the question is: *is a general class protection actually needed?*
For all data types: likely not. For libraries: i don't think so. But
other contributions to this discussion would be welcome.
Reverse question: If funcprot() is kept, will protect() will apply to
functions as well, or will be excluded? If it applies to them, how
will this cope with funcprot()?
Because presently funcprot() does not prevent silently clearing a
function, it looks unrelevant to extend its mechanism to some other data
types. But
* would it be hard to change this behavior: warning or yielding an
error /as well /when a function is cleared?
* Then, would it be hard to extend the changed behavior to any given
data type?
Samuel
_______________________________________________
dev mailing list
dev@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/dev
