Anaphase

[freezway]

Get the engine working... THEN the editor!

[Josh @ Dreamland]

Yes, that's what was decided...
Aragon is actually taking care of the makefiles now. Which makes him important. With a little luck, ENIGMA will simply pass a couple flags to the makefile and be done. Then only cross-compiler makefiles, such as that for the Wii, will be separate.

[freezway]

so... will it be released this weekend!?

[Josh @ Dreamland]

God, I hope so. If no one yet cares about interface, for which output redirection currently is STILL BROKEN, then I don't see why not. As long as the makefile gets written. I've asked Aragon to allow for parameters GRAPHICS=GL, WINDOW=WIN32, and WINDOW=XLIB. If he can add those... We'll be in good shape.

I'm going to add template tolerance and automation tomorrow. Ism can hopefully fix output redirection as soon as/before Aragon has makefile working. All else is looking good. Just fixed/seemingly finished implicit typing again. Have to make sure scope applies to it...

Presently it will flip shit if you say, for example,
if (true)
  int a = 0;
As the behavior of that is meaningless in C++ and undefined in ENIGMA. Will see what I can do about it. (It's technically as simple as finding non-'n' letter tokens and pushing the scope until ';', but...)

[freezway]

WHAT IS OUTPUT REDIRECTION?

[IsmAvatar]

Output redirection is where you print something to stdout, but instead of it being printed to the console, it gets redirected to something else, like a file or a window.

In the context of Enigma, the problem is that before, when I ran Enigma as an executable, output was put in a stream, rather than printed to stdout, and I could decide what to do with it. Now that enigma is a dll, it uses Java's stdout, so I need to redirect my own stdout to wherever I want it to go, and then put it back to terminal output afterwards.

The problem with this is that it's *my* stdout, which means that if *I* want to print something while I'm redirecting Enigma's stdout, it means that *my* output also gets redirected. This is a non-issue if I just redirect output, call the dll, and then reset output - but it's not as simple as that, because calling the dll can take time, which means that LGM would freeze while it's waiting for the dll, and you wouldn't see the output until the dll finishes, when it all comes at once.

To solve *that* problem, I would normally thread enigma (run it in its own thread, or simultaneous to LGM, rather than freezing and waiting for it to finish). However, that solution means that while I have output redirected and while Enigma is running, LGM is also running and could potentially produce output. If it does so, said output will be redirected, which is undesirable.

[freezway]

so..... its a crapshoot either way?

[IsmAvatar]

Not necessarily. It's just that each solution brings a new problem.

[Rusky]

With JNI it looks like it would be possible to pass Enigma a Java stream. However, that would require an extra layer...

[IsmAvatar]

I have no objections to using JNI, and would have liked to have used it in the first place, but I was never able to get it to work.

[luiscubal]

Could you try to get a stack trace so that, on printing, you could check where the output was coming from?

[RetroX]

GRAPHICS=GL, WINDOW=WIN32, and WINDOW=XLIB. If he can add those... We'll be in good shape.

Have DirectX graphics been implemented yet, or is that purely there for preparation?  Also, in the future, would it be possiblw to write things for ENIGMA (not necessarily you, but maybe someone else could help with it after r4 is released) for WINDOW=WIN64, WINDOW=GTK, and WINDOW=WXWIDGETS?

Yes, you can compile for Win64 with MinGW; Google mingw-w64.  It's mostly experimental, but it works.

EDIT: If ENIGMA is a DLL, what is going to be used for the GNU/Linux version?  You can't link Java to a shared library, afaik.

[Josh @ Dreamland]

Have DirectX graphics been implemented yet, or is that purely there for preparation?  Also, in the future, would it be possiblw to write things for ENIGMA (not necessarily you, but maybe someone else could help with it after r4 is released) for WINDOW=WIN64, WINDOW=GTK, and WINDOW=WXWIDGETS?

Purely preparatory. Yes, all of those would be fine if they are structured the same way as the two currently implemented systems.

EDIT: If ENIGMA is a DLL, what is going to be used for the GNU/Linux version?  You can't link Java to a shared library, afaik.

Can, and did.

[Rusky]

@luiscubal- Then you'd end up with LGM stack traces in the Enigma log.
@Retro- What would be the point of JNI without DLLs and SOs?

[RetroX]

SOs and DLLs don't operate in the same way.  DLLs have options to load functions from strings.  You can't do that with SOs, afaik.