The library documents itself · System programming
stzCapabilityCatalog
7 own methods · 0 forms written with extensions, listed under their method
the source: base/system/stzDelivery.ring(opens in a new tab) · All classes · The area reference: System programming
Under each method, its extensions (Q CS XT Z ZZ IB W U): bold and ticked, it exists; struck, it does not. The extensions and what they mean
No method of this class is run on this page: the class reaches files, the network, processes, the clock, chance or sound, and an example run here would only be an example of its effects. Each method carries the explanation the library gives of itself.
Method
Explanation, as the source carries it
init
(no comment in the source: the name reads as a sentence) initno extension
Records
(no comment in the source: the name reads as a sentence) recordsno extension
Has
(no comment in the source: the name reads as a sentence) hasno extension
Record
unknown capability -> assume Softanza-differential compute, platform-weak.no extension
DisplayOf
(no comment in the source: the name reads as a sentence) display ofno extension
SizeOf
(no comment in the source: the name reads as a sentence) size ofno extension
VectorFor
(capability, target class) -> [ vector, reason ]. The whole reasoning, legibly. Inclusive across targets: a server hosts the native engine; the heavy is offloaded; a strong non-unique capability defers to the target-platform; ergonomics on a language-runtime target become a construct, else fold into the engine. The reason keeps the capability's readable name.no extension