(mention naive approach in trplkt <= 0.9.8) |
(Add real introductory paragraph; explain compromise) |
||
| Line 1: | Line 1: | ||
'''Attributes''' are [[triple slash]] annotations inserted by the [[trplkt]] compiler. Attributes are a compromise in the design decision of the triple script ecosystem to promote development that will scale, at he cost of making source-to-bundle transformation (and back) slightly more involved than the original conception that centered only on [[triplicate-forward]] and [[triplicate-reverse]]. The adoption of attributes comes with the caveat that further iterations on the ecosystem design will seek to minimize attributes as much as possible—opting only to use them when their absence is considered untenable. |
|||
| ⚫ | |||
| ⚫ | |||
There are tentative plans to add attributes for other purposes, like [[libpacks]]. |
There are tentative plans to add attributes for other purposes, like [[libpacks]]. |
||
Revision as of 18:53, 22 June 2020
Attributes are triple slash annotations inserted by the trplkt compiler. Attributes are a compromise in the design decision of the triple script ecosystem to promote development that will scale, at he cost of making source-to-bundle transformation (and back) slightly more involved than the original conception that centered only on triplicate-forward and triplicate-reverse. The adoption of attributes comes with the caveat that further iterations on the ecosystem design will seek to minimize attributes as much as possible—opting only to use them when their absence is considered untenable.
The $path$ attribute was introduced for trplkt 0.9.9, facilitating path coherence during decompilation. In versions prior 0.9.9, trplkt doesn't recognize any attributes and relies on the aforementioned extremely straightforward but flawed approach for source transformation.
There are tentative plans to add attributes for other purposes, like libpacks.