[0.2.x] Future version plans

[Mwexim]

It's a bit early, but since we're coming closer at implementing all necessary syntax, I wanted to make this issue to already discuss future version changes.

The road-map states that this version is mainly to fix bugs that would have appeared after 0.1. I'm going to add some things to that. Version 0.3 will probably change a lot, so that's why we have to prepare our development for that version in advance.

General

These contain some of the general plans that are kept for version 0.2. These plans are stationary and won't probably be moved to a later version since they're needed in order to ensure a better environment for contributors later on.

• Operator system: @Syst3ms came up with this idea. Basically allows you to add certain operators bound to a context. When a certain context is called, the correct operator will be applied.
  • E.g. the plus-operator can now only be applied to numbers, but this overloading system would allow things like String concatenation and more.
• String literals changes: the parsing of the current VariableString is very cumbersome, in a way that it doesn't allow things like double quotes inside the string and more. These limitations should probably be enhanced.
• Improve Duration parsing and several other types.
• SectionContext implementation
• Better Converter and Comparator implementation.
• Extended support for or-lists in conditions.
• Wider implementation of tags. The current implementation is there as a placeholder, but it would be nice if we extended this feature more.
• The start of a wiki. This wiki should not contain all information, but I think it's important we attract some new contributors (possibly from the main Skript project) and guide them through. This would give the development of this project a boost since it now is kind of falling apart again due to our own responsibilities in private life. The current issue with this as well is that all code reviewal relies on Systems. For syntax classes, this is debatable, since I and Olyno both have the knowledge to review and merge these PRs ourselves. But when it comes to entirely new features and utility classes, a review of Systems is often required. If we get more people in this project, this can maybe change.
• (Extension of the CLI)

These changes will all lead up to version 0.3, where we'll change the whole variable system and possibly add a runtime error-management to the language. These features are currently in debate.

[ghostabyssnet]

I've just found out about skript-parser, I might be able to contribute to a wiki of sorts. I've been using Skript for about 5 years now but I wasn't used to its internals yet. I still have a lot to learn about standard compilers (lexical/syntax/semantic analysis and etc), but I know Skript's syntax very well.

[Mwexim]

I've just found out about skript-parser, I might be able to contribute to a wiki of sorts. I've been using Skript for about 5 years now but I wasn't used to its internals yet.

I still have a lot to learn about standard compilers (lexical/syntax/semantic analysis and etc), but I know Skript's syntax very well.

We are always open for new contributors! If you haven't already, join the Skript Chat Discord server and we'll guide you into the project. You're knowledge of Skript will particularly useful now since we're creating tests

[WeeskyBDW]

Also, a better parsing of comments. Currently, as i understand of the comment parsing method, it's not possible to comment into the line (only the entire line). Why not add a way to made multi line comments easly

[Mwexim]

Also, a better parsing of comments. Currently, as i understand of the comment parsing method, it's not possible to comment into the line (only the entire line). Why not add a way to made multi line comments easly

Honestly, replacing the comment system with something like the Java one would solve a lot of things, since hashtags would not clash. This would maybe defeat the Skript-feeling a little, so a discussion will be needed at a later time.