refactor v4 -> v5

[ericvergnaud]

No description provided.

[KvanTTT]

Also, please fill commit message with meaningfull text. I mean first pass doesn't explain changes, I'd use something like this:

Update version info (4 -> 5) and related things

Update contributors list
Use relative links in doc where it's possible
Fix Markdown formatting

[ericvergnaud]

I've reached a state where it compiles - no attempts to test
Merging so it can be used by other contributors
Partially fixes #3

[KvanTTT]

Sorry, but could you please wait for approvement from at least one member next time? It's community-driven project but not one-person-driven, isn't it?

Also, please use git squashing next time to get rid of useless commits (or squash/edit them manually). Now I see a lot of non-informative commits in antlr5 history instead of one meaningful commit.

I don't understand why we are rushing.

[ericvergnaud]

Hey, ok to squash in the future.
I'm just making sure we rapidly reach a situation where people can start contributing on a viable basis, which is where we are now i.e. the project compiles.

[KvanTTT]

Hey, ok to squash in the future.

Thanks.

I'm just making sure we rapidly reach a situation where people can start contributing on a viable basis, which is where we are now i.e. the project compiles.

I don't think changing version number affects users' contributions and experience. Project was compilable before this change.