I havn't come up with a name for it yet. but it works sorta like this. you have calls and you have frames. the frames are composed of permissions, which decide what the frame can modify and access of other frames, data, the internal data of the frame, and calls to other frames. the calls modify the permissions or data of other frames given the permissions of the given call frame.
here is a sample of what it would look like
Code: Select all
FrameUn $pr:ALL da: cl: ;
FramDue $pr: da:1,2,3,4 cl:NamedCall;
NamedCall $FrameUn:frameDue_da<4> 4 +=; /* using the permissions of FrameUn increment the data at the 4th index by 4 */
this code doesn't do anything yet though the frames are just declarations of data, and named calls don't do anything on their own. named calls have to be put inside frames. they will be called when the frame is called. anonymous calls can execute on their own. an anonymous call would look like this
Code: Select all
$FrameUn:frameDue; /*using permissions of FrameUn call frame ,and since the NamedCall call is in Framedue it calls NamedCall*/
these four statements in order would repeatedly increment frameDue data at index 4 by 4.
you can also have multiple frames in the frame section of the call. using AND, OR, and NOT as set operations. like so.
use the permisions of frameun OR framedue
use the permisions of frameun AND framedue, don't include permissions which are only in one
Code: Select all
$frameun framedue OR frametri NOT:foobarbaz;
use the permisions of frameun OR framedue then negate the permisions of frametri from the permissions set
some other rules about it, you may have noticed it is in reverse polish notation. you have to use a permission to modify data,other permissions. future plan on it, a way to manage files,writeable permissions,writing a compiler for it(lol)
