Commander X16

In theory it could be done... my first C++ compiler ran on a system with less memory and CPU than the X16, but that would mean re-writing the entire assembler and compiler...

Version 8.11 has been released. https://github.com/irmen/prog8/releases/tag/v8.11

Not sure if this is a known issue and I didn't feel like signing up to Github....it's also possible that it's my editor (Relaunch64) and/or Java I suppose.

This has happened before, but it's been a while since I did something so stupid....well, not that long...I was doing some weeding on my current project and I deleted one too many constants. Editor/Java lockup, no error messages in the log window, programmer in terror because he doesn't know what he's done!!!! I got complacent and didn't do a 'save as'...

It's unclear to me what you mean exactly, but if your editor froze suddenly it's hardly a prog8 problem.

If you managed to freeze the prog8 compiler itself though, please try to reproduce the problem and post the offending source code. There have been instances before of certain code fragments that get the compiler in an endless loop, and I'd like to fix those as obviously they shouldn't occur.

Well, I can't tell who the culprit is. I accidentally deleted a const definition, no progress in log window, can't change windows, etc., so it's like the editor is waiting for something. I finally managed to kill the 'correct' task, without killing the editor completely and got numerous errors for undefined value and editor was 'alive' again. Maybe that says what task is the offender...I think it was OpenJDK something. But as to what the root cause is???

Sounds like a problem with your editor choice and not with prog8 then. Unless you triggered a compilation step from inside the editor which hung. What editor are you using

I use Relaunch 64, to edit, which uses internal scripts to launch Prog8.

I don't know what that is, if the problem remains, maybe you could ask for help there?

I compiled with this condition from the command line, terminated normally....with 108 errors. Apparently Relaunch64 chokes on this.

Not a big deal, especially now that I can get the error list two different ways....if I remember either, the next time it happens!

Tried compiling and running rasterbars.p8 on both R39 and R41 versions of the x16emu. The compile/assembly goes OK, but the emulator hangs on either version of the emulator.

General question: Prog8 works with which versions of the emulator? Comment in prog8 source suggests address for floating point library are from R39. Does Prog8 need targets for each emulator? If not emulator version, other ideas why program hangs? Thanks!