Kay Gürtzig

@hans005 > It makes Structorizer even much more usefull for me :-) Yes but you should be aware that the Java-specific instructions won't be exportable to other languages. And some...

Interesting approach, though it would not only require that compilations for all relevant OS / CPU architecture combinations be provided but also that users will confide in the equivalence of...

@GitMensch As there is a workaround (as outlined in https://github.com/fesch/Structorizer.Desktop/issues/530#issuecomment-392655514) I haven't planned to do anything about it very soon but didn't want to discard this proposal, either. (One reason...

Just a note: should be considered in combination with #850.

Hi @calgia , This has already been proposed with #781 and is on the agenda, but its implementation will have to wait for the accomplishment of issue #800, which will...

> It even could be used for representing a named target for JUMP instruction (or is there an option to do this already?). No, and there won't be as long...

> Maybe I misunderstood the instruction that is labeled "JUMP"? Maybe. The JUMP elements are actually EXIT actions, they may leave a loop (leave/break), a routine (return) or the entire...

@GitMensch BTW: Your last question answered here ("What is the fastest way of moving parts of an algorithm into a new subroutine?") would be a neat proposal for the FAQ...

Okay, might be a "nice to have".

Anyway I won't fix it very soon. I had really hard work with the parser stuff just now...