v6.0.0

refactor!: remove support for Batch file (#86)

BREAKING CHANGE: removes .bat files.
Windows users will need to get a Bash/Linux environment. We suggest installing WSL.

v5.0.1

fix: remove BASH_SOURCE, not POSIX (#85)

v5.0.0

refactor!: remove rep-t and rep-t.bat (#84)

BREAKING CHANGE: `rep-t` and `rep-t.bat` removed.
Instead Use `rep -t` and `rep.bat -t`.

Closes #81

v4.0.2

fix: use raw strings for regex (#82)

Closes #66

v4.0.1

fix: remove use of new Java switch statements/expressions (#62)

Fixes #61, allowing PLCC to work with Java 11 or higher.

---

Co-authored-by: Timothy Fossum <[email protected]>

v4.0.0

feat: trigger release

BREAKING CHANGE: This commit is to coerce semantic-release into releasing a major release.

v3.3.1

fix: token propagation when using a custom scanner (#51)

Hi.

I just noticed that the Token.template file in the Std directory uses
an old representation of how token names get propagated into a
Token.java file when using plcc.py with the '!pattern=' flag in the
input file.

The '!pattern=' flag is typically used when writing a compiler and not
a PLCC-generated interpreter. In this case, the user must supply a
stand-alone scanner (Scan.java) instead of using the Scan.java found in
the Std library directory. Such a Scan.java file must still implement
the IScan interface, so its 'cur' method must still return a Token
object.

Token.template (instead of Token.pattern) in the Std library is used to
generate Token.java when PLCC is flagged to use a hand-crafted scanner
other than the Scan.java in the Std directory. Note that this only
applies in the case where PLCC is used to create a compiler instead of
an interpreter.

I have uploaded Token.template into the plcc.pithon.net directory. This
will *not* have any effect on any of the examples in the Code
directory, since none of these examples use the '!pattern=' flag.

Tim

Co-authored-by: Timothy Fossum <[email protected]>

v3.3.0

feat: upgrade docker dependencies (#48)

## Features

* Upgrade Java to 17 in Docker, allowing language authors to use its features when implementing languages.

## Fixes

* Test for `plcc --version` now accepts leading `v` in version numbers.

v3.2.1

fix: --version in docker

v3.2.0

fix: automate release (#45)

## fix: update CI/CD pipeline

* On pushes to PR:
    * Run automated tests.
    * Build multi-arch images tagged with PR for manual testing.
* On merge to main, release by:
    * Use Conventional Commits to determine next release number.
    * Tag commit with next release number.
    * Build multi-arch images tagged with new release number (3.2.1, 3.2, 3, and latest)
    * Create release entry in GitHub with release notes (commit messages).

## refactor: determine `--version` from git tag, then VERSION file, otherwise "Unknown"