Rochus Keller

I will implement parsers for a couple of other file formats in VerilogCreator, but in C++. Do we have access to IEEE 1497-2001?

Thanks. There is not much documentation yet because the project is evolving and there is a rather high degree of volatility in everything (though I always keep backwards compatibility in...

> I'm unable, however, to find In.Obx or Out.Obx It's compiled in the executable. Here are the definition modules: https://github.com/rochus-keller/Oberon/tree/master/oakwood. The implementation is either in C# (for the Mono engine)...

You can either generate C and do it there or use the present work-around which allows you to put the console input to a file and reference this file using...

Meanwhile I migrated CrossLine away from Qt 4 to my LeanQt version (which corresponds to Qt 5). As a side effect I offer pre-compiled versions for Windows, Linux and Mac,...

> @smarr: There seems to be an Oberon port here: Please note that the URL of the Oberon+ port is now: https://github.com/rochus-keller/Are-we-fast-yet/tree/main/Oberon Also note the FreePascal version which is work...

> I just need to figure out how to automatically detect the appropriate version so that the toolkit can work with both 2.0 and 2.1 format. There is a macro...

Thanks. Personally I'm happy with bytecode version 2.0; maybe someone can point out in what respect 2.1 is supposed to excel 2.0. Concerning my viewer: I'm aware of the command...

Thanks, will have a look at it. I wonder why nobody so far used LuaJIT as a backend for a completely different language than Lua - even a statically typed...

LuaJIT is perfect as is, personally I don't see any reason to modify it. But replacing the compiler front end i.e. reusing the backend to implement another language looks like...