[Scilab-users] All variables in scilab.ini/.scilab startup file turn protected? About predef() (1)

Samuel Gougeon sgougeon at free.fr
Thu Aug 6 18:21:07 CEST 2015


Hi all,

It seems that all variables defined in the personal startup file are now 
automatically protected and become
unclearable, with Scilab 6.0.0-a1. This could somewhat fix the bug 
http://bugzilla.scilab.org/8634
(predef() cannot be used is startup file), in an unexpected and quite 
radical way.

However, this behavior is strange: in SCI/Etc/scilab.start, there is no 
call to predef() after personal
startup file(s) is executed.

Could anyone confirm this behavior? Here is the test:

edit(SCIHOME+"/scilab.ini")
//add the line
a=1
// in the file. Save it. Quit and restart Scilab. In the new session, try
a    // should display 1
clear a   // could display a warning. Nothing is display (reported as 
http://bugzilla.scilab.org/9709 ?)
a    // still here. Not deleted = protected

// But may be "clear" is bugged... Let's try
b = 2
clear b
b   // => undefined variable. So, "clear" is OK

May we open another thread about predef()'s future...

Regards
Samuel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20150806/35cae980/attachment.htm>


More information about the users mailing list