ASPL Manual v 1.00
© 2024 by SetSphere.COM
The Element Grouping Class Container ....
The most
ASPL set variables have different shapes,
are hashes holding the information of subrgoups and elements, all of which described by their attributes,
while these hashes can be viewed as objects (one debates that such objects do not have methods)
and attributes can be tied or execC code - but they are described elsewhere in their Elem Group Class
within ASPL container, ASPL binds (links) these attributes to their corresponding processors
The user does not need to keep track of the binding process, rather just create Elem Group Class and define the attribute of the elem
-attributes "point1,t" "point2,t" "point3,t"
and can further add named processors and restrict their DOMAIN
"mean123,c,__mean123 point1 point2 point3 /[0.0,4.99] 1-5feet/[5.0,6.5] 5-6feet/>6.5 above7feet/"
■ Metagrouping Tied Attributes
Tied attributes allow to specify a domain or RANGE. The metagroup will parse a RANGE, it is written as
-attributes "point1,t" "point2,t" "point3,t"
which says that the attribute with names point1 point2 point3 are tied attribute
"mean123,c,__mean123 point1 point2 point3 /[0.0,4.99] 1-5feet/[5.0,6.5] 5-6feet/>6.5 above7feet/"
which says that the attribute mean123 is CODE with subroutine __mean123 to be executed, and point1 point2 point3 are
passed as actual parameters; also the range
The following example shows how ASPL variables get to exist once they are assigned
aspl> a1 = ggdir /tmp/aa1
(result is assigned to a1)
aspl> a2 = ggdir /tmp/aa2
(result is assigned to a2)
aspl> a12 = f& a1 a2
(a12 is assigned the intersection of a1 and a2)
aspl> v
(print the variables)
① aspl> c123 = c& a1 a2 a3
(c123 is assigned all checksums intersections of a1 a2 a3)
② aspl> adisplay c123
(print out c123)
aspl> av c123
(view internals of set variable c123)
③ Just dump the rest to a file
AS BEING SET IN THE SHELL: -------------------------- ASPL_CONFIG=/root/WS,WS3,10,10,10,1000,30,2,0,0,0