Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementation of New functions "isprotected", "protect", and "unprotect" #366

Merged
merged 1 commit into from
Feb 17, 2018

Conversation

rdbyk
Copy link
Owner

@rdbyk rdbyk commented Feb 17, 2018

fixes #41

isprotected, protect, and unprotect provide means for dealling with protection of variables, each accepts one array of strings as input argument ...

--> protect("a")

protect: Wrong value "a" in argument #1: An existent variable expected.

--> a=123
 a  = 

   123.


--> protect a

--> isprotected("a")
 ans  =

  T


--> a=456

Redefining permanent variable.

--> a
 a  = 

   123.


--> unprotect("a")

--> isprotected("a")
 ans  =

  F


--> a=456
 a  = 

   456.


--> isprotected("%nan")
 ans  =

  T


--> unprotect("%nan") // Not a good idea at all, but will it work?

--> %nan
 %nan  = 

   Nan


--> %nan=0
 %nan  = 

   0.

--> %nan = 0/0
 %nan  = 

   Nan

@rdbyk rdbyk merged commit bc6d997 into master Feb 17, 2018
@rdbyk rdbyk deleted the protect_vars branch February 17, 2018 23:01
@rdbyk rdbyk changed the title Implementation of New functions "isprotected", "protect", and "unprotect"" Implementation of New functions "isprotected", "protect", and "unprotect" Feb 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implemenent proper user interface for variable protection
1 participant