xvm VS seed7

Parts of Ecstasy are now implemented in Ecstasy. Here's the Lexer, for example.

Ecstasy

A Future reference has the various capabilities that you'd imagine, taking lambdas for thenDo(), whenComplete(), etc. The reference, in the above example, is a local variable, so you just obtain it using the C-style & operator:

FWIW - here is the stage manager code that I referred to.

Ecstasy (xtclang.org): Currently working on session management for a cloud-based HTTP back end. Not exactly compiler or language stuff, but it certainly is exercising the compiler and language.

I prefer to make my AST nodes fairly rich, and let them do the brunt of the work themselves. Instead of the 5 lines of code above, the assignment statement node in Ecstasy is over 1000 LOC. But it handles everything from initial validation through the MLIR emission.

No, not that specific project. It's our own Mid Level Intermediate Representation (or Mid Level Intermediate Language), aka MLIR/MLIL. Here's a snapshot of the operators.

Ecstasy project on Github: https://github.com/xtclang/xvm

Quite a few improvements in Ecstasy over the past month:

Early on, we had the This keyword, and its meaning was "this type". So if a method on class Collection was declared as This add(Element), it meant that the method returned the auto-narrowing type of this. We later changed it from This to Collection (or whatever the class name is) and added the Collection! (non-narrowing) form, because there were syntactic needs (e.g. inner and outer auto-narrowing class references) that could not be covered by This. We evaluated a few different options, and we liked (and still like) the result that we came up with. That said, I still wish we had a This keyword (see the 5th bullet point) for the "this type", but 🤷‍♂️.

Seed7 at GitHub

Yes, I am regularly working on improvements for Seed7. The changes are checked in at GitHub (see here for the list of commits) and once a month I do a release which is announced at r/seed7.

It all depends on the circumstances behind. In the beginning the core-js maintainer had no family and now he has. When I released Seed7 I already had a family. It was clear that my job had to support my family and my hobby (GitHub link).

I improved the explanation in read_me.txt. Now make test is recommended but considered optional as it can also be done later. With make test you can be sure that most of the language works as expected (graphics, sockets and some other things are not tested). Explaining that su should not be used for some commands would probably just add confusion. :-)

If you don't like the Seed7 Homepage at SF you can go to GitHub, Rosetta Code or r/seed7 instead.

Beside the Seed7 Homepage there other sources of information. Several example programs can be found at Rosetta Code. Announcements and discussions take place at r/seed7. Discussions are also in the Seed7 mailing list and announcements are also here. Seed7 is also at GitHub and in Wikipedia.

I just use Emacs without any syntax highlighting for Seed7. Others contributed syntax highlighting files. For vim there is seed7/doc/seed7.vim and seed7/doc/sd7.vim. There is also seed7/doc/seed7.syn and seed7/doc/seed7.uew.

You can find all the released versions of Seed7 at SF and GitHub. There is also r/seed7 where I do announcements.

I invented the program chkccomp.c to find out all properties of C, its run-time and other C libraries (operating system + third party). When you compile Seed7 this program creates hundreds of little test programs that are compiled linked and executed. With that information chkccomp.c writes several hundred lines of property macros to a file named version.h, Other projects use shell scripts for this purpose (./configure comes into mind), but these scripts usually do not work for Windows.

For Seed7 I implemented my own version of CommandLineToArgvW. This function is used if the original one is not available. As mentioned in the article it turned out as much more complicated than expected.