Implementing versioning

[ArthaTi]

I'm planning to implement versioning by moving the large command switch to a different file, for example v1.1. When a backwards-incompatible update is planned, a new file is created, for example v1.2. Syntax highlighting with red marked errors wouldn't be possible for older versions.

In the online interpreter, there will be a select box with all available versions, so you can choose the one you want.

The URL will change a bit, though existing links won't be affected. An example permalink to a new version would be #v1.2/YiYaYgYe – currently permalinks always begin with an uppercase letter.

Yes, this is what releases, tags and branches are for, though GitHub pages doesn't support versioning. If the project had to use a better versioning system, Pepe would need to be hosted on my website. Of course it can, but it will break permalinks, for example.

[u-ndefine]

Nice idea, but how about the links without version numbers?

[ArthaTi]

@u-ndefine They will refer to earliest available version, just like they do now.

[ArthaTi]

I'll be working on this now, on the rewrite branch.