[j-nsp] How is SLAX "version" statement internally used?

[Martin T]

On Thu, Feb 1, 2018 at 7:30 PM, Phil Shafer <phil at juniper.net> wrote:
> Martin T writes:
>>"version" statement in SLAX script is mandatory and argument for
>>version statement has to be either 1.0 or 1.1. Based on my testing,
>>1.2 works as well for example in Junos 16.1R2.11. However, is there
>>any difference between "version 1.0" and "version 1.1"? For example,
>>in Junos 16.1R2.11 one could define "version 1.0" and still use
>>functionality introduced in SLAX 1.1 like mutable variables or for
>>loops. How is "version" statement used by cscript/mgd?
>
> At this point, it's strictly informational.  I don't want to "break"
> a script because it uses a new feature, so I don't do enforcement.
> Mainly it's used for output during "slaxproc --write-version"
> processing, which can convert between versions.
>
> http://libslax.readthedocs.io/en/latest/distribution.html#slaxproc-the-slax-processor
>
> http://libslax.readthedocs.io/en/latest/notes.html#slax-version-information
>
> Thanks,
>  Phil

Understood. Thanks!


regards,
Martin