llModifyMe and llViewMe

Don't know if this has been suggested before, or if it is even possible, but I had an idea about a new set of scripting calls that could be used to give scripters more power. It's call llModifyMe and llViewMe. What these two functions would do would allow the scripter to choose which parts of his code could be viewed, or even modified, so that when they sell their scripts, they aren't stuck either choosing the script to be open or closed. If they want a majority of their script to be closed, this gives them the option to allow people to view a specific part of the code, or change something in one part of the code. A much better option than leaving a script locked, and having to make any changes themselves for their clients.

For example, say someone made a Brand new door script, one that works in a different way than the normal door scripts. They don't want this script to be open source, but they want whoever buys the script to be able to modify a few of the calls (say that there is a detectedAV call so only certain people can open the door), the scripter can set that particular function to llModifyMe, so the owner can change that one function to whatever they may need. And the rest of the script can still be locked and not viewable.

There were two ways I was thinking this could happen. One way would be as a global variable, so that anytime the script need to call a specific function, that function could be modified or viewed by the owner. The other way is a "per-function" call, i.e., the function begins with llModifyMe(llFunctioncall, text to explain what they may need to change); This will give the scripters more power over how their script can be used, and allow the owner to still be able to fit the script to their needs.

That would be kinda usefull, however.. We already have a better solution that that.
Use a configuration notecard.. Something like

________
Position = <1,0,0>
Jedi = TRUE
...
...
_____
ect.

Sure its more work for us scripting types, but it still seems like the better option. Then the script wont have to be recompiled, or worse, they break it and delete lines on accident.

That's true, but then again, you can put a disclaimer up saying that any problems would be the owners responsibility, and not the scripters. It'd be up to the scripter if they wanted to fix this problem or not.

The llViewMe call could be used to refresh people's minds on certain variables, ecspecially in regards to channels on listen scripts. As of now, there is only one way (that I know of) to figure out what channel a script is listening to (and it's not really easy), so that could be extremly useful. Perhaps in an update in the future. Of course, if you were worried about people breaking the script that way, outside of notes in the script itself, perhaps have a revert call, to where the whole script is reverted back to a scripter's specified settings, sort of like a memory, of course, that would eat up scripters resources, but I don't imagine people needing to use it too much.

It's called llMessageLinked. Keep a script open with the code you wish to let others modify, and use llMessageLinked to RPCishly call library functions in other scripts.

voting llMessageLinked()