Rockstar code version handling

I have an idea, how could we smoothly, but still poetically perfectly handle versions in Rockstar code. It is similar to #pragma handling, or Oracle DB execution hints: hide them in comments.

I will tweak the comment handling, salt a bit with poetic literals, and we can get a construct like this:

(# a never-ending love #) 

The text is wrapped into (# and #) special comment braces, and it represents - if interpreted as poetic literal - 114. The value could be used as a code, for example, it would mean that it requires Rockstar language version 1.4 or greater. We could have a code table, for example, 100-199 represents code version, 200-299 something else, the rest is reserved for future use, etc.

It would require no new language elements, and lay as a meta-data in a comment. But it is still poetic, giving an upbeat to the poem.

Still, it's optional, old codes may run without it, defaulting to Rockstar 1.0 behavior. It's even possible to change the parser or interpreter behavior runtime, or fail fast if that version is not supported.