The Stack with Objects and Functions Programming Language, a pure stack-based reverse-polish-notation functional and object-oriented experimental programming language.
The Eclipse IDE build system is not very flexible and portable. Although Visual Studio Code has extensions which support it, it would be much easier if we used Gradle to build the entire thing.
Right now, only four build targets would be required:
quickbuild: which only builds /src and does not test. Runs considerably faster than full build.
build: which builds /src into /bin and /test into /testbins, then runs test, otherwise fails. May also create jars.
run: which runs the CLI class from the /bin files. (see below)
test: which runs the JUnit test suite, possibly customized via some controller code invoking JUnit.
The main issue with using the builtin java systems of gradle is that they have a hard time handling the module system and the java module plugin messes with the command line of a java application run with it, i.e. it can only be used for building, not for running SOF.
Implementing this would mostly just involve creating the build and settings files, removing the Eclipse files like ".classpath" and ".project" and documenting the build targets in the README and wiki.
The Eclipse IDE build system is not very flexible and portable. Although Visual Studio Code has extensions which support it, it would be much easier if we used Gradle to build the entire thing.
Right now, only four build targets would be required:
quickbuild
: which only builds /src and does not test. Runs considerably faster than full build.build
: which builds /src into /bin and /test into /testbins, then runstest
, otherwise fails. May also create jars.run
: which runs the CLI class from the /bin files. (see below)test
: which runs the JUnit test suite, possibly customized via some controller code invoking JUnit.The main issue with using the builtin java systems of gradle is that they have a hard time handling the module system and the java module plugin messes with the command line of a java application run with it, i.e. it can only be used for building, not for running SOF.
Implementing this would mostly just involve creating the build and settings files, removing the Eclipse files like ".classpath" and ".project" and documenting the build targets in the README and wiki.