Repository navigation
Releases
Peaseblossom 0.15.0
Peaseblossom 0.15.0: poc, an Oberon-2 compiler with an LLVM back end and a back end for VAX/VMS 5.5-2.
This software is developed with the aid of AI.
New:
- Indexing a string constant, on both back ends. A string constant of m characters, declared in the module or imported, is a read-only
ARRAY m+1 OF CHAR: withCONST hex = "0123456789ABCDEF",hex[0]is aCHARconstant, usable in aCONSTdeclaration or aCASElabel,hex[i]is index-checked (trap 2), andLEN(hex)is the constant 17.-strictrejects it. The Reference Guide, "Indexing a string constant", has the rules. In.Peekgives the next character of standard input, left unread, so the nextPeek,Charor other read starts with it; at the end of the inputDoneis FALSE.OutStr'sAttwins (CharAt,StringAt,LnAt,IntAt,HexAt,CardAt,CardHexAt,RealAt,LongRealAt) append atVAR pos, the index of the string's 0X, and move it past what they append, so a long string is built without searching for its end each time.- memcheck no longer reports the collector's stack scan: under valgrind the collector marks each stack word it reads as defined, in a copy, so a program's own use of an undefined value is still reported. Run natively, it costs about 0.1% more instructions (GcBench).
- 32-bit x86 Linux gets
-march=i686on every clang command. clang's default there, pentium4, used SSE2 for reals and copies even at-O0, so programs died on a Pentium II; reals there now use the x87. The BSDs keep their own defaults.
Fixed:
- The collector no longer frees a reachable object of a record with no fields on 64-bit targets.
In.Int,In.LongInt,InStr.IntandInStr.LongIntclearDonefor a number too large for the variable, rather than truncating it.Fileson 32-bit targets keeps a seek position of 2^32 or more, rather than truncating it.MAX(SYSTEM.ADDRESS)andMIN(SYSTEM.ADDRESS)are accepted, and are constants.- poc no longer crashes on a module or procedure with no name (
MODULE 1;, a UTF-8 byte-order mark beforeMODULE) whoseENDhas one; it reports the errors. - The VAX back end indexes a structured constant with a variable (
table[i]), which it refused. - The LLVM back end folds a selection with constant selectors from a structured constant (
squares[2],M.origin.x), rather than loading it behind index checks.
Compatibility: poc refuses a library (poc -library) written by another version of poc, so rebuild your libraries with 0.15.0. -install-library reinstalls them over the old copies. A program built for the VAX against the installed libraries needs a VMS installation from the kits of the same version.
Runs on: Linux (Fedora 44, x86_64; Debian 13, amd64 and arm64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386). It needs clang 19 or later. poc for the VAX runs on VAX/VMS 5.5-2.
Building from the tarball: the tarball carries poc's own LLVM IR, so clang and GNU make alone build it. No other Oberon compiler is needed. It is also the way to install poc on any Linux distribution or BSD without a package for it.
tar xzf peaseblossom-0.15.0.tar.gz && cd peaseblossom-0.15.0
make installable && make install
make installable-vax && make install-vax # for poc -target vax-dec-vms
INSTALL.md has the details. doc/users-guide.md is how to use poc, doc/reference-guide.md and poc(1) say exactly what it accepts, and doc/vax-vms-guide.md is poc for VAX/VMS. Alternatively, poc can be built using Vishap Oberon (voc).
Files: the tarball, its SHA-256 sum (.sha256) and its GPG signature (.asc); the two VAX/VMS kits, POC-0-15-0.COM and POC-VMS-0-15-0.COM; POC-EXAMPLES-0-15-0.COM and POC-EXAMPLES-SOURCE-0-15-0.COM, the VAX/VMS Guide's examples as kits, built and as source; peaseblossom for Fedora 44 (x86_64 RPM and source RPM, signed), Debian 13 (amd64 and arm64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386); peaseblossom-vax for Fedora 44 (noarch RPM, signed), Debian 13, FreeBSD 15.1 and OpenBSD 7.9 (one package each, for any architecture) and NetBSD 11.0 (amd64 and i386); and SHA256SUMS, the SHA-256 sum of every file, with its signature SHA256SUMS.asc.
Installing a package: check it against SHA256SUMS, then, as root: dnf install ./peaseblossom-0.15.0-1.fc44.x86_64.rpm (Fedora), apt install ./peaseblossom-0.15.0-1-debian13-amd64.deb or -arm64.deb (Debian), pkg add ./peaseblossom-0.15.0-freebsd15.1-amd64.pkg or -arm64.pkg (FreeBSD), or pkg_add ./peaseblossom-0.15.0-netbsd11.0-amd64.tgz or -i386.tgz (NetBSD, with pkgsrc's clang). OpenBSD's pkg_add accepts a package only under its own name, so download it under that name, the i386 or the amd64 one:
ftp -o peaseblossom-0.15.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.15.0/peaseblossom-0.15.0-openbsd7.9-amd64.tgz
pkg_add -D unsigned ./peaseblossom-0.15.0.tgz
peaseblossom-vax installs the same way, after peaseblossom: dnf install ./peaseblossom-vax-0.15.0-1.fc44.noarch.rpm, apt install ./peaseblossom-vax-0.15.0-1-debian13-all.deb, pkg add ./peaseblossom-vax-0.15.0-freebsd15.1.pkg, pkg_add ./peaseblossom-vax-0.15.0-netbsd11.0-amd64.tgz or -i386.tgz, and on OpenBSD:
ftp -o peaseblossom-vax-0.15.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.15.0/peaseblossom-vax-0.15.0-openbsd7.9.tgz
pkg_add -D unsigned ./peaseblossom-vax-0.15.0.tgz
INSTALL.md, section 5, has the details.
Installing on VAX/VMS: copy the two kits to VMS in ASCII mode (with FTP, ascii before put), then unpack them: each kit is a DCL command procedure that unpacks itself into the directory it is run in, so make an empty directory for poc, set default to it, and execute the base kit and then the STARLET kit there:
$ CREATE/DIRECTORY [.POC]
$ SET DEFAULT [.POC]
$ @[-]POC-0-15-0
$ @[-]POC-VMS-0-15-0
Then run @BUILD and @SETUP. The VAX/VMS Guide, chapter 1, has the steps.
Trying the examples on VAX/VMS: copy POC-EXAMPLES-0-15-0.COM to VMS in ASCII mode, and run it in an empty directory, then @BUILD, which builds every program of the VAX/VMS Guide there; no installed poc is needed:
$ CREATE/DIRECTORY [.EXAMPLES]
$ SET DEFAULT [.EXAMPLES]
$ @[-]POC-EXAMPLES-0-15-0
$ @BUILD
$ RUN HELLO
With poc installed on VMS, POC-EXAMPLES-SOURCE-0-15-0.COM goes the same way, and its @BUILD builds the programs with the installed poc:
$ CREATE/DIRECTORY [.EXAMPLES]
$ SET DEFAULT [.EXAMPLES]
$ @[-]POC-EXAMPLES-SOURCE-0-15-0
$ @BUILD
$ RUN HELLO
Peaseblossom 0.14.0
Peaseblossom 0.14.0: poc, an Oberon-2 compiler with an LLVM back end and a back end for VAX/VMS 5.5-2.
This software is developed with the aid of AI.
New:
StopRequests, a runtime module on both back ends, so that a program can stop cleanly when asked, as a server finishes its connections, with no C of its own.Catchcatches SIGINT and SIGTERM (on VAX/VMS, CTRL/C atSYS$COMMAND), each once: the next request of the same kind ends the program at once, so whoever asked can insist.Latestsays which request came (none,interrupt,terminate), andSetNotifierinstalls a procedure called when one comes, which may set the program's own variables or post aTasks.Event, so a task awaiting it learns of the request at once, even while every task waits. The Reference Guide's runtime chapter has its interface.
Fixed:
Tasks' deadlines on VAX/VMS no longer move when the clock is set. VMS 5.5 keeps local time, set back or forward at the changes of daylight saving time, andTasksmeasured its deadlines and timers with$GETTIM. It now readsEXE$GL_ABSTIM_TICS, the executive's count of 10 ms ticks since boot.POCRTLis linked withSYS$SYSTEM:SYS.STB/SELECTIVE_SEARCHfor it, and passes that on to every program linked against it; a program that takesTasksfromrtl/vax's source names it with-link(the VAX/VMS Guide, "Tasks").TaskInputon VAX/VMS reads a mailbox in pieces no larger than the mailbox's messages (DVI$_DEVBUFSIZ). A larger read failed withSS$_MBTOOSML, whichTaskInputtook for the end of the input.TaskInputon POSIX reads again afterEINTR, rather than taking a read a caught signal interrupts for the end of the input.- A task's first
Platform.GetClockno longer overruns a small task's stack on NetBSD amd64 and OpenBSD i386, where libc's firstlocaltimeloads the time zone on the stack, needing more than 32 KiB:Coroutinesloads the time zones on the main stack before it makes the first coroutine's.
Compatibility: the compiler itself is unchanged, but poc refuses a library (poc -library) written by another version of poc, so rebuild your libraries with 0.14.0. -install-library reinstalls them over the old copies. A program built for the VAX against the installed libraries needs a VMS installation from the kits of the same version. On VAX/VMS, an image that uses Tasks (POCRTL.EXE among them) records the version of the executive's part it reads (SYS$K_STABLE), and VMS refuses to run it (SS$_SYSVERDIF) where that part's major version differs, until it is linked again there; @BUILD links it on the system it runs on.
Runs on: Linux (Fedora 44, x86_64; Debian 13, amd64 and arm64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386). It needs clang 19 or later. poc for the VAX runs on VAX/VMS 5.5-2.
Building from the tarball: the tarball carries poc's own LLVM IR, so clang and GNU make alone build it. No other Oberon compiler is needed. It is also the way to install poc on any Linux distribution or BSD without a package for it.
tar xzf peaseblossom-0.14.0.tar.gz && cd peaseblossom-0.14.0
make installable && make install
make installable-vax && make install-vax # for poc -target vax-dec-vms
INSTALL.md has the details. doc/users-guide.md is how to use poc, doc/reference-guide.md and poc(1) say exactly what it accepts, and doc/vax-vms-guide.md is poc for VAX/VMS. Alternatively, poc can be built using Vishap Oberon (voc).
Files: the tarball, its SHA-256 sum (.sha256) and its GPG signature (.asc); the two VAX/VMS kits, POC-0-14-0.COM and POC-VMS-0-14-0.COM; POC-EXAMPLES-0-14-0.COM and POC-EXAMPLES-SOURCE-0-14-0.COM, the VAX/VMS Guide's examples as kits, built and as source; peaseblossom for Fedora 44 (x86_64 RPM and source RPM, signed), Debian 13 (amd64 and arm64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386); peaseblossom-vax for Fedora 44 (noarch RPM, signed), Debian 13, FreeBSD 15.1 and OpenBSD 7.9 (one package each, for any architecture) and NetBSD 11.0 (amd64 and i386); and SHA256SUMS, the SHA-256 sum of every file, with its signature SHA256SUMS.asc.
Installing a package: check it against SHA256SUMS, then, as root: dnf install ./peaseblossom-0.14.0-1.fc44.x86_64.rpm (Fedora), apt install ./peaseblossom-0.14.0-1-debian13-amd64.deb or -arm64.deb (Debian), pkg add ./peaseblossom-0.14.0-freebsd15.1-amd64.pkg or -arm64.pkg (FreeBSD), or pkg_add ./peaseblossom-0.14.0-netbsd11.0-amd64.tgz or -i386.tgz (NetBSD, with pkgsrc's clang). OpenBSD's pkg_add accepts a package only under its own name, so download it under that name, the i386 or the amd64 one:
ftp -o peaseblossom-0.14.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.14.0/peaseblossom-0.14.0-openbsd7.9-amd64.tgz
pkg_add -D unsigned ./peaseblossom-0.14.0.tgz
peaseblossom-vax installs the same way, after peaseblossom: dnf install ./peaseblossom-vax-0.14.0-1.fc44.noarch.rpm, apt install ./peaseblossom-vax-0.14.0-1-debian13-all.deb, pkg add ./peaseblossom-vax-0.14.0-freebsd15.1.pkg, pkg_add ./peaseblossom-vax-0.14.0-netbsd11.0-amd64.tgz or -i386.tgz, and on OpenBSD:
ftp -o peaseblossom-vax-0.14.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.14.0/peaseblossom-vax-0.14.0-openbsd7.9.tgz
pkg_add -D unsigned ./peaseblossom-vax-0.14.0.tgz
INSTALL.md, section 5, has the details.
Installing on VAX/VMS: copy the two kits to VMS in ASCII mode (with FTP, ascii before put), then unpack them: each kit is a DCL command procedure that unpacks itself into the directory it is run in, so make an empty directory for poc, set default to it, and execute the base kit and then the STARLET kit there:
$ CREATE/DIRECTORY [.POC]
$ SET DEFAULT [.POC]
$ @[-]POC-0-14-0
$ @[-]POC-VMS-0-14-0
Then run @BUILD and @SETUP. The VAX/VMS Guide, chapter 1, has the steps.
Trying the examples on VAX/VMS: copy POC-EXAMPLES-0-14-0.COM to VMS in ASCII mode, and run it in an empty directory, then @BUILD, which builds every program of the VAX/VMS Guide there; no installed poc is needed:
$ CREATE/DIRECTORY [.EXAMPLES]
$ SET DEFAULT [.EXAMPLES]
$ @[-]POC-EXAMPLES-0-14-0
$ @BUILD
$ RUN HELLO
With poc installed on VMS, POC-EXAMPLES-SOURCE-0-14-0.COM goes the same way, and its @BUILD builds the programs with the installed poc:
$ CREATE/DIRECTORY [.EXAMPLES]
$ SET DEFAULT [.EXAMPLES]
$ @[-]POC-EXAMPLES-SOURCE-0-14-0
$ @BUILD
$ RUN HELLO
Peaseblossom 0.13.1
Peaseblossom 0.13.1: poc, an Oberon-2 compiler with an LLVM back end and a back end for VAX/VMS 5.5-2.
This software is developed with the aid of AI.
Fixed:
- Coroutines and tasks under valgrind. valgrind's memcheck took a switch from one coroutine's stack to another's for a large push or pop, and reported false errors in programs using
CoroutinesorTasks. Each coroutine's stack is now registered with valgrind, so memcheck follows a switch, and such a program runs clean under it. Outside valgrind this costs a few instructions per stack made or freed. The runtime includes valgrind's own header,valgrind.h(licence bzip2-1.0.6, BSD-style), as the packages now record. VAX/VMS is unaffected.
Compatibility: the compiler itself is unchanged, and only the runtime changed, but poc refuses a library (poc -library) written by another version of poc, so rebuild your libraries with 0.13.1. -install-library reinstalls them over the old copies. A program built for the VAX against the installed libraries needs a VMS installation from the kits of the same version.
Runs on: Linux (Fedora 44, x86_64; Debian 13, amd64 and arm64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386). It needs clang 19 or later. poc for the VAX runs on VAX/VMS 5.5-2.
Building from the tarball: the tarball carries poc's own LLVM IR, so clang and GNU make alone build it. No other Oberon compiler is needed. It is also the way to install poc on any Linux distribution or BSD without a package for it.
tar xzf peaseblossom-0.13.1.tar.gz && cd peaseblossom-0.13.1
make installable && make install
make installable-vax && make install-vax # for poc -target vax-dec-vms
INSTALL.md has the details. doc/users-guide.md is how to use poc, doc/reference-guide.md and poc(1) say exactly what it accepts, and doc/vax-vms-guide.md is poc for VAX/VMS. Alternatively, poc can be built using Vishap Oberon (voc).
Files: the tarball, its SHA-256 sum (.sha256) and its GPG signature (.asc); the two VAX/VMS kits, POC-0-13-1.COM and POC-VMS-0-13-1.COM; POC-EXAMPLES-0-13-1.COM and POC-EXAMPLES-SOURCE-0-13-1.COM, the VAX/VMS Guide's examples as kits, built and as source; peaseblossom for Fedora 44 (x86_64 RPM and source RPM, signed), Debian 13 (amd64 and arm64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386); peaseblossom-vax for Fedora 44 (noarch RPM, signed), Debian 13, FreeBSD 15.1 and OpenBSD 7.9 (one package each, for any architecture) and NetBSD 11.0 (amd64 and i386); and SHA256SUMS, the SHA-256 sum of every file, with its signature SHA256SUMS.asc.
Installing a package: check it against SHA256SUMS, then, as root: dnf install ./peaseblossom-0.13.1-1.fc44.x86_64.rpm (Fedora), apt install ./peaseblossom-0.13.1-1-debian13-amd64.deb or -arm64.deb (Debian), pkg add ./peaseblossom-0.13.1-freebsd15.1-amd64.pkg or -arm64.pkg (FreeBSD), or pkg_add ./peaseblossom-0.13.1-netbsd11.0-amd64.tgz or -i386.tgz (NetBSD, with pkgsrc's clang). OpenBSD's pkg_add accepts a package only under its own name, so download it under that name, the i386 or the amd64 one:
ftp -o peaseblossom-0.13.1.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.13.1/peaseblossom-0.13.1-openbsd7.9-amd64.tgz
pkg_add -D unsigned ./peaseblossom-0.13.1.tgz
peaseblossom-vax installs the same way, after peaseblossom: dnf install ./peaseblossom-vax-0.13.1-1.fc44.noarch.rpm, apt install ./peaseblossom-vax-0.13.1-1-debian13-all.deb, pkg add ./peaseblossom-vax-0.13.1-freebsd15.1.pkg, pkg_add ./peaseblossom-vax-0.13.1-netbsd11.0-amd64.tgz or -i386.tgz, and on OpenBSD:
ftp -o peaseblossom-vax-0.13.1.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.13.1/peaseblossom-vax-0.13.1-openbsd7.9.tgz
pkg_add -D unsigned ./peaseblossom-vax-0.13.1.tgz
INSTALL.md, section 5, has the details.
Installing on VAX/VMS: copy the two kits to VMS in ASCII mode (with FTP, ascii before put), then unpack them: each kit is a DCL command procedure that unpacks itself into the directory it is run in, so make an empty directory for poc, set default to it, and execute the base kit and then the STARLET kit there:
$ CREATE/DIRECTORY [.POC]
$ SET DEFAULT [.POC]
$ @[-]POC-0-13-1
$ @[-]POC-VMS-0-13-1
Then run @BUILD and @SETUP. The VAX/VMS Guide, chapter 1, has the steps.
Trying the examples on VAX/VMS: copy POC-EXAMPLES-0-13-1.COM to VMS in ASCII mode, and run it in an empty directory, then @BUILD, which builds every program of the VAX/VMS Guide there; no installed poc is needed:
$ CREATE/DIRECTORY [.EXAMPLES]
$ SET DEFAULT [.EXAMPLES]
$ @[-]POC-EXAMPLES-0-13-1
$ @BUILD
$ RUN HELLO
With poc installed on VMS, POC-EXAMPLES-SOURCE-0-13-1.COM goes the same way, and its @BUILD builds the programs with the installed poc:
$ CREATE/DIRECTORY [.EXAMPLES]
$ SET DEFAULT [.EXAMPLES]
$ @[-]POC-EXAMPLES-SOURCE-0-13-1
$ @BUILD
$ RUN HELLO
Peaseblossom 0.13.0
Peaseblossom 0.13.0: poc, an Oberon-2 compiler with an LLVM back end and a back end for VAX/VMS 5.5-2.
This software is developed with the aid of AI.
New:
- Timed descriptor waits in
Tasks.AwaitReadableFor(fd, ms)andAwaitWritableFor(fd, ms)wait for a file descriptor to become ready, asAwaitReadableandAwaitWritabledo, but for at mostmsmilliseconds, and return whether it became ready. A network program can give a connection a deadline, and a server can stop. LikeAwaitReadable, they are POSIX's: on VMS they trap (20), and a$QIO's AST posts instead. - The VAX/VMS Guide's examples as source. A second kit,
POC-EXAMPLES-SOURCE-0-13-0.COM, holds the examples' Oberon-2 source instead of MACRO-32 written on Unix, for a VMS site with poc installed: itsBUILD.COMcompiles each program with the installed poc (the foreign commandPOC), and builds again only a program whose.EXEis missing or older than its source (@BUILD ALLbuilds every one,@BUILD NAMEthat one). Run again, the kit unpacks only the files that are missing, so a changed source is kept, and a site can change a program and build it again. QueensandWordSetsin both examples kits. The User's Guide's two coroutine programs, which run on VMS unchanged, are now inPOC-EXAMPLESandPOC-EXAMPLES-SOURCE.
Compatibility: the compiler itself is unchanged, but poc refuses a library (poc -library) written by another version of poc, so rebuild your libraries with 0.13.0. -install-library reinstalls them over the old copies. A program built for the VAX against the installed libraries needs a VMS installation from the kits of the same version.
Runs on: Linux (Fedora 44, x86_64; Debian 13, amd64 and arm64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386). It needs clang 19 or later. poc for the VAX runs on VAX/VMS 5.5-2.
Building from the tarball: the tarball carries poc's own LLVM IR, so clang and GNU make alone build it. No other Oberon compiler is needed. It is also the way to install poc on any Linux distribution or BSD without a package for it.
tar xzf peaseblossom-0.13.0.tar.gz && cd peaseblossom-0.13.0
make installable && make install
make installable-vax && make install-vax # for poc -target vax-dec-vms
INSTALL.md has the details. doc/users-guide.md is how to use poc, doc/reference-guide.md and poc(1) say exactly what it accepts, and doc/vax-vms-guide.md is poc for VAX/VMS. Alternatively, poc can be built using Vishap Oberon (voc).
Files: the tarball, its SHA-256 sum (.sha256) and its GPG signature (.asc); the two VAX/VMS kits, POC-0-13-0.COM and POC-VMS-0-13-0.COM; POC-EXAMPLES-0-13-0.COM and POC-EXAMPLES-SOURCE-0-13-0.COM, the VAX/VMS Guide's examples as kits, built and as source; peaseblossom for Fedora 44 (x86_64 RPM and source RPM, signed), Debian 13 (amd64 and arm64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386); peaseblossom-vax for Fedora 44 (noarch RPM, signed), Debian 13, FreeBSD 15.1 and OpenBSD 7.9 (one package each, for any architecture) and NetBSD 11.0 (amd64 and i386); and SHA256SUMS, the SHA-256 sum of every file, with its signature SHA256SUMS.asc.
Installing a package: check it against SHA256SUMS, then, as root: dnf install ./peaseblossom-0.13.0-1.fc44.x86_64.rpm (Fedora), apt install ./peaseblossom-0.13.0-1-debian13-amd64.deb or -arm64.deb (Debian), pkg add ./peaseblossom-0.13.0-freebsd15.1-amd64.pkg or -arm64.pkg (FreeBSD), or pkg_add ./peaseblossom-0.13.0-netbsd11.0-amd64.tgz or -i386.tgz (NetBSD, with pkgsrc's clang). OpenBSD's pkg_add accepts a package only under its own name, so download it under that name, the i386 or the amd64 one:
ftp -o peaseblossom-0.13.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.13.0/peaseblossom-0.13.0-openbsd7.9-amd64.tgz
pkg_add -D unsigned ./peaseblossom-0.13.0.tgz
peaseblossom-vax installs the same way, after peaseblossom: dnf install ./peaseblossom-vax-0.13.0-1.fc44.noarch.rpm, apt install ./peaseblossom-vax-0.13.0-1-debian13-all.deb, pkg add ./peaseblossom-vax-0.13.0-freebsd15.1.pkg, pkg_add ./peaseblossom-vax-0.13.0-netbsd11.0-amd64.tgz or -i386.tgz, and on OpenBSD:
ftp -o peaseblossom-vax-0.13.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.13.0/peaseblossom-vax-0.13.0-openbsd7.9.tgz
pkg_add -D unsigned ./peaseblossom-vax-0.13.0.tgz
INSTALL.md, section 5, has the details.
Installing on VAX/VMS: copy the two kits to VMS in ASCII mode (with FTP, ascii before put), then unpack them: each kit is a DCL command procedure that unpacks itself into the directory it is run in, so make an empty directory for poc, set default to it, and execute the base kit and then the STARLET kit there:
$ CREATE/DIRECTORY [.POC]
$ SET DEFAULT [.POC]
$ @[-]POC-0-13-0
$ @[-]POC-VMS-0-13-0
Then run @BUILD and @SETUP. The VAX/VMS Guide, chapter 1, has the steps.
Trying the examples on VAX/VMS: copy POC-EXAMPLES-0-13-0.COM to VMS in ASCII mode, and run it in an empty directory, then @BUILD, which builds every program of the VAX/VMS Guide there; no installed poc is needed:
$ CREATE/DIRECTORY [.EXAMPLES]
$ SET DEFAULT [.EXAMPLES]
$ @[-]POC-EXAMPLES-0-13-0
$ @BUILD
$ RUN HELLO
With poc installed on VMS, POC-EXAMPLES-SOURCE-0-13-0.COM goes the same way, and its @BUILD builds the programs with the installed poc:
$ CREATE/DIRECTORY [.EXAMPLES]
$ SET DEFAULT [.EXAMPLES]
$ @[-]POC-EXAMPLES-SOURCE-0-13-0
$ @BUILD
$ RUN HELLO
Peaseblossom 0.12.0
Peaseblossom 0.12.0: poc, an Oberon-2 compiler with an LLVM back end and a back end for VAX/VMS 5.5-2.
This software is developed with the aid of AI.
New:
- Coroutines. A runtime module with Oakwood's
InitandTransfer, plusFreeandDefaultStackSize, on both back ends. Each coroutine has a fixed stack with a guard page, and the collector scans every suspended stack. A body that returns, misuse (a freed or uninitialized target, freeing the running coroutine,Transferin a finalizer, a signal handler or an AST) and a stack that cannot be allocated each trap with their own status (16, 17, 18). The User's Guide's chapter 11 describes it, with two examples,WordSetsandQueens, which run unchanged on VMS; the VAX/VMS Guide says what differs there. - Tasks. Cooperative tasks over
Coroutines, the same Oberon on both back ends: a task is an extension ofTasks.TaskDescwith aRunmethod. It has Mesa-style conditions, mutexes, channels of extensible records, a receive-onlySelect,Afteras a timeout channel,Sleep,Join, andPost, which signal handlers and VMS ASTs use to wake a task. When every task waits, the program waits inpoll(POSIX) or$HIBER(VMS) instead of spinning.AwaitReadableandAwaitWritablewait on a file descriptor (POSIX), andTaskInputreads standard input as a task. Nothing preempts a task, and a blocking call stops them all. The User's Guide's chapter 12 and the VAX/VMS Guide describe it, with examples. - Threads and signal handlers. The rules are now written down: a program has one thread, and a
Platformsignal handler only sets the program's own variables, which the main line reads withSYSTEM.GET. - Debian packages.
peaseblossomfor Debian 13 (trixie) on amd64 and arm64, andpeaseblossom-vax, built frompackaging/debian. make examplesandmake examples-vaxbuild the guides' example programs: the User's Guide's inbuild/examples, and the VAX/VMS Guide's asbuild/POC-EXAMPLES-0-12-0.COM, a kit that unpacks itself on VMS, where@BUILDbuilds them all with no installed poc. This release carries that kit too.
Compatibility: the compiler itself is unchanged, but poc refuses a library (poc -library) written by another version of poc, so rebuild your libraries with 0.12.0. -install-library reinstalls them over the old copies. A program built for the VAX against the installed libraries needs a VMS installation from the kits of the same version.
Runs on: Linux (Fedora 44, x86_64; Debian 13, amd64 and arm64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386). It needs clang 19 or later. poc for the VAX runs on VAX/VMS 5.5-2.
Building from the tarball: the tarball carries poc's own LLVM IR, so clang and GNU make alone build it. No other Oberon compiler is needed. It is also the way to install poc on any Linux distribution or BSD without a package for it.
tar xzf peaseblossom-0.12.0.tar.gz && cd peaseblossom-0.12.0
make installable && make install
make installable-vax && make install-vax # for poc -target vax-dec-vms
INSTALL.md has the details. doc/users-guide.md is how to use poc, doc/reference-guide.md and poc(1) say exactly what it accepts, and doc/vax-vms-guide.md is poc for VAX/VMS. Alternatively, poc can be built using Vishap Oberon (voc).
Files: the tarball, its SHA-256 sum (.sha256) and its GPG signature (.asc); the two VAX/VMS kits, POC-0-12-0.COM and POC-VMS-0-12-0.COM; POC-EXAMPLES-0-12-0.COM, the VAX/VMS Guide's examples as a kit; peaseblossom for Fedora 44 (x86_64 RPM and source RPM, signed), Debian 13 (amd64 and arm64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386); peaseblossom-vax for Fedora 44 (noarch RPM, signed), Debian 13, FreeBSD 15.1 and OpenBSD 7.9 (one package each, for any architecture) and NetBSD 11.0 (amd64 and i386); and SHA256SUMS, the SHA-256 sum of every file, with its signature SHA256SUMS.asc.
Installing a package: check it against SHA256SUMS, then, as root: dnf install ./peaseblossom-0.12.0-1.fc44.x86_64.rpm (Fedora), apt install ./peaseblossom-0.12.0-1-debian13-amd64.deb or -arm64.deb (Debian), pkg add ./peaseblossom-0.12.0-freebsd15.1-amd64.pkg or -arm64.pkg (FreeBSD), or pkg_add ./peaseblossom-0.12.0-netbsd11.0-amd64.tgz or -i386.tgz (NetBSD, with pkgsrc's clang). OpenBSD's pkg_add accepts a package only under its own name, so download it under that name, the i386 or the amd64 one:
ftp -o peaseblossom-0.12.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.12.0/peaseblossom-0.12.0-openbsd7.9-amd64.tgz
pkg_add -D unsigned ./peaseblossom-0.12.0.tgz
peaseblossom-vax installs the same way, after peaseblossom: dnf install ./peaseblossom-vax-0.12.0-1.fc44.noarch.rpm, apt install ./peaseblossom-vax-0.12.0-1-debian13-all.deb, pkg add ./peaseblossom-vax-0.12.0-freebsd15.1.pkg, pkg_add ./peaseblossom-vax-0.12.0-netbsd11.0-amd64.tgz or -i386.tgz, and on OpenBSD:
ftp -o peaseblossom-vax-0.12.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.12.0/peaseblossom-vax-0.12.0-openbsd7.9.tgz
pkg_add -D unsigned ./peaseblossom-vax-0.12.0.tgz
INSTALL.md, section 5, has the details.
Installing on VAX/VMS: copy the two kits to VMS in ASCII mode (with FTP, ascii before put), then unpack them: each kit is a DCL command procedure that unpacks itself into the directory it is run in, so make an empty directory for poc, set default to it, and execute the base kit and then the STARLET kit there:
$ CREATE/DIRECTORY [.POC]
$ SET DEFAULT [.POC]
$ @[-]POC-0-12-0
$ @[-]POC-VMS-0-12-0
Then run @BUILD and @SETUP. The VAX/VMS Guide, chapter 1, has the steps.
Trying the examples on VAX/VMS: copy POC-EXAMPLES-0-12-0.COM to VMS in ASCII mode, and run it in an empty directory, then @BUILD, which builds every program of the VAX/VMS Guide there; no installed poc is needed:
$ CREATE/DIRECTORY [.EXAMPLES]
$ SET DEFAULT [.EXAMPLES]
$ @[-]POC-EXAMPLES-0-12-0
$ @BUILD
$ RUN HELLO
Peaseblossom 0.11.2
Peaseblossom 0.11.2: poc, an Oberon-2 compiler with an LLVM back end and a back end for VAX/VMS 5.5-2. This release adds BUILDVIAOBJ.COM to the VAX/VMS kit. The compiler itself is the same as in 0.11.1.
This software is developed with the aid of AI.
New on VAX/VMS: the base kit has BUILDVIAOBJ.COM. After @BUILD, @BUILDVIAOBJ INSTALL rebuilds poc from its own source through its object back end, and checks that the poc so built compiles that source again to the same objects. Then it installs the new poc in [.BIN]POC.EXE, and keeps the kit's poc as [.BIN]POC-KIT.EXE. @BUILDVIAOBJ CHECK builds and checks without installing, and @BUILDVIAOBJ with no parameter only builds. Each compilation of poc takes from a quarter of an hour to three quarters of one on an emulated MicroVAX 3900, and the procedure needs a paging file quota of 60,000 pages. The VAX/VMS Guide, chapter 1 and chapter 17, has the details. The guide now gives poc's memory as about 16 MB rather than 90 MB, and the kit's README.TXT now says correctly that FULL.ARGS writes objects.
Compatibility: poc refuses a library (poc -library) written by another version of poc, so rebuild your libraries with 0.11.2. -install-library reinstalls them over the old copies. A program built for the VAX against the installed libraries needs a VMS installation from the kits of the same version. The kits are still MACRO-32 (text), so @BUILD still assembles poc on VMS from MACRO-32.
Runs on: Linux (Fedora 44, x86_64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386). It needs clang 19 or later. poc for the VAX runs on VAX/VMS 5.5-2.
Building from the tarball: the tarball carries poc's own LLVM IR, so clang and GNU make alone build it. No other Oberon compiler is needed. It is also the way to install poc on any Linux distribution or BSD without a package for it.
tar xzf peaseblossom-0.11.2.tar.gz && cd peaseblossom-0.11.2
make installable && make install
make installable-vax && make install-vax # for poc -target vax-dec-vms
INSTALL.md has the details. doc/users-guide.md is how to use poc, doc/reference-guide.md and poc(1) say exactly what it accepts, and doc/vax-vms-guide.md is poc for VAX/VMS. Alternatively, poc can be built using Vishap Oberon (voc).
Files: the tarball, its SHA-256 sum (.sha256) and its GPG signature (.asc); the two VAX/VMS kits, POC-0-11-2.COM and POC-VMS-0-11-2.COM; peaseblossom for Fedora 44 (x86_64 RPM and source RPM, signed), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386); peaseblossom-vax for Fedora 44 (noarch RPM, signed), FreeBSD 15.1 and OpenBSD 7.9 (one package each, for any architecture) and NetBSD 11.0 (amd64 and i386); and SHA256SUMS, the SHA-256 sum of every file, with its signature SHA256SUMS.asc.
Installing a package: check it against SHA256SUMS, then, as root: dnf install ./peaseblossom-0.11.2-1.fc44.x86_64.rpm (Fedora), pkg add ./peaseblossom-0.11.2-freebsd15.1-amd64.pkg or -arm64.pkg (FreeBSD), or pkg_add ./peaseblossom-0.11.2-netbsd11.0-amd64.tgz or -i386.tgz (NetBSD, with pkgsrc's clang). OpenBSD's pkg_add accepts a package only under its own name, so download it under that name, the i386 or the amd64 one:
ftp -o peaseblossom-0.11.2.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.11.2/peaseblossom-0.11.2-openbsd7.9-amd64.tgz
pkg_add -D unsigned ./peaseblossom-0.11.2.tgz
peaseblossom-vax installs the same way, after peaseblossom: dnf install ./peaseblossom-vax-0.11.2-1.fc44.noarch.rpm, pkg add ./peaseblossom-vax-0.11.2-freebsd15.1.pkg, pkg_add ./peaseblossom-vax-0.11.2-netbsd11.0-amd64.tgz or -i386.tgz, and on OpenBSD:
ftp -o peaseblossom-vax-0.11.2.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.11.2/peaseblossom-vax-0.11.2-openbsd7.9.tgz
pkg_add -D unsigned ./peaseblossom-vax-0.11.2.tgz
INSTALL.md, section 5, has the details.
Installing on VAX/VMS: copy the two kits to VMS in ASCII mode (with FTP, ascii before put), then unpack them: each kit is a DCL command procedure that unpacks itself into the directory it is run in, so make an empty directory for poc, set default to it, and execute the base kit and then the STARLET kit there:
$ CREATE/DIRECTORY [.POC]
$ SET DEFAULT [.POC]
$ @[-]POC-0-11-2
$ @[-]POC-VMS-0-11-2
Then run @BUILD and @SETUP, and if you like, @BUILDVIAOBJ INSTALL. The VAX/VMS Guide, chapter 1, has the steps.
Peaseblossom 0.11.1
Peaseblossom 0.11.1: poc, an Oberon-2 compiler with an LLVM back end and a back end for VAX/VMS 5.5-2, with one fix, to a string literal in an array index.
This software is developed with the aid of AI.
Fixed: on LLVM targets, a string literal passed to a procedure called inside an array index, as in a[F("ab")] := 1 or x := a[F("ab")], was referenced in the generated code but never defined, so the build failed with clang's "use of undefined value '@.str...'". The same was true of a literal in a set constructor's element, {F("ab")}, and in the index of a procedure variable called as a statement, p[F("ab")](x). All of these are now emitted. The VAX back end never had the bug.
Compatibility: poc refuses a library (poc -library) written by another version of poc, so rebuild your libraries with 0.11.1. -install-library reinstalls them over the old copies. A program built for the VAX against the installed libraries needs a VMS installation from the kits of the same version. The kits are still MACRO-32 (text), so @BUILD still assembles poc on VMS from MACRO-32.
Runs on: Linux (Fedora 44, x86_64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386). It needs clang 19 or later. poc for the VAX runs on VAX/VMS 5.5-2.
Building from the tarball: the tarball carries poc's own LLVM IR, so clang and GNU make alone build it. No other Oberon compiler is needed. It is also the way to install poc on any Linux distribution or BSD without a package for it.
tar xzf peaseblossom-0.11.1.tar.gz && cd peaseblossom-0.11.1
make installable && make install
make installable-vax && make install-vax # for poc -target vax-dec-vms
INSTALL.md has the details. doc/users-guide.md is how to use poc, doc/reference-guide.md and poc(1) say exactly what it accepts, and doc/vax-vms-guide.md is poc for VAX/VMS. Alternatively, poc can be built using Vishap Oberon (voc).
Files: the tarball, its SHA-256 sum (.sha256) and its GPG signature (.asc); the two VAX/VMS kits, POC-0-11-1.COM and POC-VMS-0-11-1.COM; peaseblossom for Fedora 44 (x86_64 RPM and source RPM, signed), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386); peaseblossom-vax for Fedora 44 (noarch RPM, signed), FreeBSD 15.1 and OpenBSD 7.9 (one package each, for any architecture) and NetBSD 11.0 (amd64 and i386); and SHA256SUMS, the SHA-256 sum of every file, with its signature SHA256SUMS.asc.
Installing a package: check it against SHA256SUMS, then, as root: dnf install ./peaseblossom-0.11.1-1.fc44.x86_64.rpm (Fedora), pkg add ./peaseblossom-0.11.1-freebsd15.1-amd64.pkg or -arm64.pkg (FreeBSD), or pkg_add ./peaseblossom-0.11.1-netbsd11.0-amd64.tgz or -i386.tgz (NetBSD, with pkgsrc's clang). OpenBSD's pkg_add accepts a package only under its own name, so download it under that name, the i386 or the amd64 one:
ftp -o peaseblossom-0.11.1.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.11.1/peaseblossom-0.11.1-openbsd7.9-amd64.tgz
pkg_add -D unsigned ./peaseblossom-0.11.1.tgz
peaseblossom-vax installs the same way, after peaseblossom: dnf install ./peaseblossom-vax-0.11.1-1.fc44.noarch.rpm, pkg add ./peaseblossom-vax-0.11.1-freebsd15.1.pkg, pkg_add ./peaseblossom-vax-0.11.1-netbsd11.0-amd64.tgz or -i386.tgz, and on OpenBSD:
ftp -o peaseblossom-vax-0.11.1.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.11.1/peaseblossom-vax-0.11.1-openbsd7.9.tgz
pkg_add -D unsigned ./peaseblossom-vax-0.11.1.tgz
INSTALL.md, section 5, has the details.
Installing on VAX/VMS: copy the two kits to VMS in ASCII mode (with FTP, ascii before put), then unpack them: each kit is a DCL command procedure that unpacks itself into the directory it is run in, so make an empty directory for poc, set default to it, and execute the base kit and then the STARLET kit there:
$ CREATE/DIRECTORY [.POC]
$ SET DEFAULT [.POC]
$ @[-]POC-0-11-1
$ @[-]POC-VMS-0-11-1
Then run @BUILD and @SETUP. The VAX/VMS Guide, chapter 1, has the steps.
Peaseblossom 0.11.0
Peaseblossom 0.11.0: poc, an Oberon-2 compiler with an LLVM back end and a back end for VAX/VMS 5.5-2.
This software is developed with the aid of AI.
New:
- Predeclared unsigned types.
SHORTCARD,CARDINAL,LONGCARDandHUGECARDhave as many bits in each size model asSHORTINT,INTEGER,LONGINTandHUGEINT. They follow every rule ofSYSTEM.CARD8..CARD64andSYSTEM.CARD, which stay and mix with them by inclusion, so noSYSTEMimport is needed. Both back ends have them, and-strictrejects them. - Predeclared
VAL(T, x)is the way between the signed and unsigned families with no import: it givesSYSTEM.VAL's bits on integers of either family, traps a value that does not fit under-range-checks, refuses a constant that does not, and is itself a constant.-strictrejects it. In.HugeCardandInStr.HugeCardread aHUGECARD.- Libraries without a shared object (LLVM).
poc -no-shared-library -library greet Greet.Modbuilds only the archive, for code that cannot go in a shared library, such as a binding to a static library built without-fPIC.-shared-librarieslinks such a library's archive and warns, and a library with a shared object cannot need one without: poc refuses that, naming both. The User's Guide, section 5, has the details.
Changed: a function procedure called as a statement is now a compile-time error, as the report requires. poc used to accept it and drop the result. Such a program must now use the result, or assign it to a variable.
Fixed:
- A
.symfile is no longer left behind after an error found in a module's interface, or after an import of a file that declares another module. An importer could otherwise have used the bad.symwith no error. - An import of a file that declares a module whose name doesn't match the file name now says so.
-compileno longer calls a file on the command line an imported module.- The repository checks out on a case-insensitive file system such as macOS's: two tracked files in the
vax-buildfixture differed only in case.
Compatibility: besides the new error above, poc refuses a library (poc -library) written by another version of poc, so rebuild your libraries with 0.11.0. -install-library reinstalls them over the old copies. A program built for the VAX against the installed libraries needs a VMS installation from the kits of the same version. The kits are still MACRO-32 (text), so @BUILD still assembles poc on VMS from MACRO-32.
Runs on: Linux (Fedora 44, x86_64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386). It needs clang 19 or later. poc for the VAX runs on VAX/VMS 5.5-2.
Building from the tarball: the tarball carries poc's own LLVM IR, so clang and GNU make alone build it. No other Oberon compiler is needed. It is also the way to install poc on any Linux distribution or BSD without a package for it.
tar xzf peaseblossom-0.11.0.tar.gz && cd peaseblossom-0.11.0
make installable && make install
make installable-vax && make install-vax # for poc -target vax-dec-vms
INSTALL.md has the details. doc/users-guide.md is how to use poc, doc/reference-guide.md and poc(1) say exactly what it accepts, and doc/vax-vms-guide.md is poc for VAX/VMS. Alternatively, poc can be built using Vishap Oberon (voc).
Files: the tarball, its SHA-256 sum (.sha256) and its GPG signature (.asc); the two VAX/VMS kits, POC-0-11-0.COM and POC-VMS-0-11-0.COM; peaseblossom for Fedora 44 (x86_64 RPM and source RPM, signed), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386); peaseblossom-vax for Fedora 44 (noarch RPM, signed), FreeBSD 15.1 and OpenBSD 7.9 (one package each, for any architecture) and NetBSD 11.0 (amd64 and i386); and SHA256SUMS, the SHA-256 sum of every file, with its signature SHA256SUMS.asc.
Installing a package: check it against SHA256SUMS, then, as root: dnf install ./peaseblossom-0.11.0-1.fc44.x86_64.rpm (Fedora), pkg add ./peaseblossom-0.11.0-freebsd15.1-amd64.pkg or -arm64.pkg (FreeBSD), or pkg_add ./peaseblossom-0.11.0-netbsd11.0-amd64.tgz or -i386.tgz (NetBSD, with pkgsrc's clang). OpenBSD's pkg_add accepts a package only under its own name, so download it under that name, the i386 or the amd64 one:
ftp -o peaseblossom-0.11.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.11.0/peaseblossom-0.11.0-openbsd7.9-amd64.tgz
pkg_add -D unsigned ./peaseblossom-0.11.0.tgz
peaseblossom-vax installs the same way, after peaseblossom: dnf install ./peaseblossom-vax-0.11.0-1.fc44.noarch.rpm, pkg add ./peaseblossom-vax-0.11.0-freebsd15.1.pkg, pkg_add ./peaseblossom-vax-0.11.0-netbsd11.0-amd64.tgz or -i386.tgz, and on OpenBSD:
ftp -o peaseblossom-vax-0.11.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.11.0/peaseblossom-vax-0.11.0-openbsd7.9.tgz
pkg_add -D unsigned ./peaseblossom-vax-0.11.0.tgz
INSTALL.md, section 5, has the details.
Installing on VAX/VMS: copy the two kits to VMS in ASCII mode (with FTP, ascii before put), then unpack them: each kit is a DCL command procedure that unpacks itself into the directory it is run in, so make an empty directory for poc, set default to it, and execute the base kit and then the STARLET kit there:
$ CREATE/DIRECTORY [.POC]
$ SET DEFAULT [.POC]
$ @[-]POC-0-11-0
$ @[-]POC-VMS-0-11-0
Then run @BUILD and @SETUP. The VAX/VMS Guide, chapter 1, has the steps.
Peaseblossom 0.10.1
Peaseblossom 0.10.1: poc, an Oberon-2 compiler with an LLVM back end and a back end for VAX/VMS 5.5-2, with one fix, to the collector of a program whose only NEW is in a library.
This software is developed with the aid of AI.
Fixed: on VAX/VMS, a program whose main module calls no NEW, but which uses a library module that does, never had the collector scan the machine stack: its main set up the collector only when a module compiled in the same run of poc called NEW. A collection could then free objects held only in local variables, and the program would ACCVIO or read freed memory. A library's manifest now records which of its modules allocate (NEW or SYSTEM.NEW), and a program sets up the collector whenever any of its modules does, on both back ends. On LLVM targets, where the collector was set up correctly, a program that never allocates no longer links it.
Compatibility: poc refuses a library (poc -library) written by another version of poc, so rebuild your libraries with 0.10.1. -install-library reinstalls them over the old copies. A program built for the VAX against the installed libraries needs a VMS installation from the kits of the same version. The kits are still MACRO-32 (text), so @BUILD still assembles poc on VMS from MACRO-32.
Runs on: Linux (Fedora 44, x86_64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386). It needs clang 19 or later. poc for the VAX runs on VAX/VMS 5.5-2.
Building from the tarball: the tarball carries poc's own LLVM IR, so clang and GNU make alone build it. No other Oberon compiler is needed. It is also the way to install poc on any Linux distribution or BSD without a package for it.
tar xzf peaseblossom-0.10.1.tar.gz && cd peaseblossom-0.10.1
make installable && make install
make installable-vax && make install-vax # for poc -target vax-dec-vms
INSTALL.md has the details. doc/users-guide.md is how to use poc, doc/reference-guide.md and poc(1) say exactly what it accepts, and doc/vax-vms-guide.md is poc for VAX/VMS. Alternatively, poc can be built using Vishap Oberon (voc).
Files: the tarball, its SHA-256 sum (.sha256) and its GPG signature (.asc); the two VAX/VMS kits, POC-0-10-1.COM and POC-VMS-0-10-1.COM; peaseblossom for Fedora 44 (x86_64 RPM and source RPM, signed), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386); peaseblossom-vax for Fedora 44 (noarch RPM, signed), FreeBSD 15.1 and OpenBSD 7.9 (one package each, for any architecture) and NetBSD 11.0 (amd64 and i386); and SHA256SUMS, the SHA-256 sum of every file, with its signature SHA256SUMS.asc.
Installing a package: check it against SHA256SUMS, then, as root: dnf install ./peaseblossom-0.10.1-1.fc44.x86_64.rpm (Fedora), pkg add ./peaseblossom-0.10.1-freebsd15.1-amd64.pkg or -arm64.pkg (FreeBSD), or pkg_add ./peaseblossom-0.10.1-netbsd11.0-amd64.tgz or -i386.tgz (NetBSD, with pkgsrc's clang). OpenBSD's pkg_add accepts a package only under its own name, so download it under that name, the i386 or the amd64 one:
ftp -o peaseblossom-0.10.1.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.10.1/peaseblossom-0.10.1-openbsd7.9-amd64.tgz
pkg_add -D unsigned ./peaseblossom-0.10.1.tgz
peaseblossom-vax installs the same way, after peaseblossom: dnf install ./peaseblossom-vax-0.10.1-1.fc44.noarch.rpm, pkg add ./peaseblossom-vax-0.10.1-freebsd15.1.pkg, pkg_add ./peaseblossom-vax-0.10.1-netbsd11.0-amd64.tgz or -i386.tgz, and on OpenBSD:
ftp -o peaseblossom-vax-0.10.1.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.10.1/peaseblossom-vax-0.10.1-openbsd7.9.tgz
pkg_add -D unsigned ./peaseblossom-vax-0.10.1.tgz
INSTALL.md, section 5, has the details.
Installing on VAX/VMS: copy the two kits to VMS in ASCII mode (with FTP, ascii before put), then unpack them: each kit is a DCL command procedure that unpacks itself into the directory it is run in, so make an empty directory for poc, set default to it, and execute the base kit and then the STARLET kit there:
$ CREATE/DIRECTORY [.POC]
$ SET DEFAULT [.POC]
$ @[-]POC-0-10-1
$ @[-]POC-VMS-0-10-1
Then run @BUILD and @SETUP. The VAX/VMS Guide, chapter 1, has the steps.
Peaseblossom 0.10.0
Peaseblossom 0.10.0: poc, an Oberon-2 compiler with an LLVM back end and a back end for VAX/VMS 5.5-2, which now takes object files and external variables, for linking with code written in other languages.
This software is developed with the aid of AI.
New:
- External variables.
VAR ["C", "environ"] environment-: SYSTEM.ADDRESS;declares storage that another object defines, under its linkage name (the second string, used as written; without it, each identifier is its own name). The variable is read, written, passed and given toSYSTEM.ADRin place. poc allocates, zeroes and initializes nothing for it, and it is not a root for the collector, so a tracedPOINTER TOanywhere in its type is an error. The LLVM back end takes["C"], and the VAX back end takes["VMS", "NAME"], whose name is in capitals, such as a shareable image's universal data. An importing module uses the linkage name, and-strictrejects the attribute. The Reference Guide, "External variables", has the rules. - Object files on the command line.
- LLVM: a
.owith no.symbeside it is linked by-buildafter the modules' objects, and put in the library by-library. The library's manifest records it, so a program linked with the library gets it. - VAX/VMS:
-buildand-librarytake.objfiles.-libraryputs them in the.OLBand links them into the shareable image, with their entry points made universal. On Linux and the BSDs, an object made on VMS must be in the counted form: run the newOBJCONVERT -COUNTEDon VMS, then fetch the result by FTP in binary mode.
- LLVM: a
- Linker options for VAX/VMS. Each
-linkargument is a line of the options file given toLINK. A.optamong the files is a Linker options file whose lines are added in the same way. A library records both, so every program linked with it gets them. -target vax-dec-vmsrefuses the LLVM-only options:-opt,-lto,-rebuild,-static,-c-flag,-verbose,-emit-llvm-irand-dump-llvm-types. It used to ignore them; poc on VMS already refused them.
Fixed: a -link argument was cut to 255 characters. It is now read whole, up to the 2,042 characters a library manifest's line holds, and a longer one is refused.
Compatibility: poc refuses a library (poc -library) written by another version of poc, so rebuild your libraries with 0.10.0. -install-library reinstalls them over the old copies. A program built for the VAX against the installed libraries needs a VMS installation from the kits of the same version. The kits are still MACRO-32 (text), so @BUILD still assembles poc on VMS from MACRO-32.
Runs on: Linux (Fedora 44, x86_64), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386). It needs clang 19 or later. poc for the VAX runs on VAX/VMS 5.5-2.
Building from the tarball: the tarball carries poc's own LLVM IR, so clang and GNU make alone build it. No other Oberon compiler is needed. It is also the way to install poc on any Linux distribution or BSD without a package for it.
tar xzf peaseblossom-0.10.0.tar.gz && cd peaseblossom-0.10.0
make installable && make install
make installable-vax && make install-vax # for poc -target vax-dec-vms
INSTALL.md has the details. doc/users-guide.md is how to use poc, doc/reference-guide.md and poc(1) say exactly what it accepts, and doc/vax-vms-guide.md is poc for VAX/VMS. Alternatively, poc can be built using Vishap Oberon (voc).
Files: the tarball, its SHA-256 sum (.sha256) and its GPG signature (.asc); the two VAX/VMS kits, POC-0-10-0.COM and POC-VMS-0-10-0.COM; peaseblossom for Fedora 44 (x86_64 RPM and source RPM, signed), FreeBSD 15.1 (amd64 and arm64), OpenBSD 7.9 (i386 and amd64) and NetBSD 11.0 (amd64 and i386); peaseblossom-vax for Fedora 44 (noarch RPM, signed), FreeBSD 15.1 and OpenBSD 7.9 (one package each, for any architecture) and NetBSD 11.0 (amd64 and i386); and SHA256SUMS, the SHA-256 sum of every file, with its signature SHA256SUMS.asc.
Installing a package: check it against SHA256SUMS, then, as root: dnf install ./peaseblossom-0.10.0-1.fc44.x86_64.rpm (Fedora), pkg add ./peaseblossom-0.10.0-freebsd15.1-amd64.pkg or -arm64.pkg (FreeBSD), or pkg_add ./peaseblossom-0.10.0-netbsd11.0-amd64.tgz or -i386.tgz (NetBSD, with pkgsrc's clang). OpenBSD's pkg_add accepts a package only under its own name, so download it under that name, the i386 or the amd64 one:
ftp -o peaseblossom-0.10.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.10.0/peaseblossom-0.10.0-openbsd7.9-amd64.tgz
pkg_add -D unsigned ./peaseblossom-0.10.0.tgz
peaseblossom-vax installs the same way, after peaseblossom: dnf install ./peaseblossom-vax-0.10.0-1.fc44.noarch.rpm, pkg add ./peaseblossom-vax-0.10.0-freebsd15.1.pkg, pkg_add ./peaseblossom-vax-0.10.0-netbsd11.0-amd64.tgz or -i386.tgz, and on OpenBSD:
ftp -o peaseblossom-vax-0.10.0.tgz https://github.com/tkurtbond/peaseblossom/releases/download/v0.10.0/peaseblossom-vax-0.10.0-openbsd7.9.tgz
pkg_add -D unsigned ./peaseblossom-vax-0.10.0.tgz
INSTALL.md, section 5, has the details.
Installing on VAX/VMS: copy the two kits to VMS in ASCII mode (with FTP, ascii before put), then unpack them: each kit is a DCL command procedure that unpacks itself into the directory it is run in, so make an empty directory for poc, set default to it, and execute the base kit and then the STARLET kit there:
$ CREATE/DIRECTORY [.POC]
$ SET DEFAULT [.POC]
$ @[-]POC-0-10-0
$ @[-]POC-VMS-0-10-0
Then run @BUILD and @SETUP. The VAX/VMS Guide, chapter 1, has the steps.