> On May 3, 2017, at 1:01 AM, Martin Carlberg <
mar...@oops.se> wrote:
>
> Hi!
>
> The first thing that comes into my mind is that when we compile Objective-J code we load everything into the runtime. This means that any code that is on the base level in a Objective-J file will be executed.
>
> So if you type "while (true);" on a line outside of functions and class declarations (for example on the first line of the file) the compiler will just loop. It does not need to be this obvious as you can have any javascript code that will be executed. The narwhal process should spends 100% cpu when it is running as I guess it is.
It has not, actually. Never exceeded around a few percent.
> Try to temporary remove any code that is outside functions and class declarations and check if it will not choke.
>
> You can also add ”print” statements on the base level inside the file to see how far the compilation has progressed. For example: 'print(”Martin was here”);’
I ran it via the command line and it appears to be a bug in XcodeCapp bug. It completed fine but carped about a large number of missing identifiers (just needed @global defines). For whatever reason, XcodeCapp is not reporting these errors at all as it spans numerous source files I have been actively working on without a single message. I will file a bug.