Pretty buggy editor
The editor is pretty much a bonus, and a work in progress. It is maybe maybe not good enough yet for using beyond simple source code edition (what I mean is that it certainly can't be seen yet as a full blwon IDE, but is already much better than using notepad, or any editor that has no syntax highlighting for BriskSL). Other than that, if you find sever bugs I'd be thankfull for you to report them on the BriskVM forum.By the way, at one point I may open source the editor, so that if anyone feels like he could enhance it further.
which already confused me because I think it by itself is confused
In all honesty I don't think the script language manual is that bad. There are necessarily some typos left here and there, and I correct them as they are reported. Thanks to report the error about the extension method, I fixed the docs, it will be in the next release (ad is already fixed on the online help). If you have other complaints I invite you to detail how you think I can enhance it, this would very much help me. (note: language, not the other thing, which should be merged so it makes sense)
Here I have to disagree. I separated the language manual and the library manual on purpose, because the angle is not the same, and so that you can redistribute the script language manual along with your briskvm-powered application (a modder doesn't care about the brisvm library, all he cares about is the script language).And the "!flag" thing (that is, "command set options") are something a modder as no way to modify, it's totally in the handds of the devloper that integrates BriskVM, hence why it's explained in the BriskVM manual, not in the script language manual. That said, I alsa have included notes here and there in the language manual to warn that feature X is only available if option Y is specified in the command set.
I think your problem may be due to the fact that you specified repository directories inside the script editor. When repositories are specified, *only* scripts (or command sets, or modules) within the repository are accepted. This is for security reasons (this is a bit like in Java where classes must all be within the classpath). Your problem with bvmcmd may be the same : if you specified a repository earlier on the command line, no script outside this repository will be accepted.
Reading the documentation off your site is painful. Extremely painful.
I agree it could be more comfortable. But come on, *all* the docs comme with the trial version, so it's seriously no big deal. Thanks to report though, it confirms my own thoughts.For the grammar: no, I have no formal grammar for the language (well I have one, but it's not the "clean grammar", as it's the grammar I actually use for the parsing and compiling, which is unnecessarily complex for mere reading).