Wanted: Linux user to compile pre-alpha

[PaulBlay]

Originally Posted by PaulBlay

I'm trying to get Open Watcom to work for me at the moment.

Not having much luck yet. Some of the warnings appear incorrect (to my inexperienced eye). For example the following line

		if (parse_under && (ke.key >=0 && ke.key <= 32))

gets a "Warning! W124: Comparison result always 1", but I can't see what's wrong with it.

I also have a whole bunch of

Symbol 'SCREEN_REGION' has been defined, but not referenced

warnings, but it's being used like

menu_layout(menu, &SCREEN_REGION);

all over the place. Does 'referenced' mean something else than what I think it does?

[Pete Mack]

@paul:
Those warnings are both extremely dubious (ie: wrong). I wouldn't trust the compiler to generate reliable code.

Why pick yet another obsolete compiler? Just use gcc on the command line for a reference, even if you still want to use DevCC for an IDE.


Or go all the way and install Visual C++ express. It's a huge (~800MB) download, but it's an extremely good IDE and compiler.

[PaulBlay]

Originally Posted by Pete Mack

@paul:
Those warnings are both extremely dubious (ie: wrong). I wouldn't trust the compiler to generate reliable code.

Why pick yet another obsolete compiler?

To be fair its last release was in February 2009 so it wasn't exactly obvious to me that it was obsolete.

Or go all the way and install Visual C++ express. It's a huge (~800MB) download, but it's an extremely good IDE and compiler.

I've got Visual C++ installed, it was on the list of compilers to try eventually. I guess I just have bad judgement in picking which ones to try.

[takkaria]

Originally Posted by PaulBlay

Not having much luck yet. Some of the warnings appear incorrect (to my inexperienced eye). For example the following line

		if (parse_under && (ke.key >=0 && ke.key <= 32))

gets a "Warning! W124: Comparison result always 1", but I can't see what's wrong with it.

Looks like ke.key is unsigned on Watcom, when it's not elsewhere. Hence, "ke.key >= 0" will always be true.

I also have a whole bunch of

Symbol 'SCREEN_REGION' has been defined, but not referenced

warnings, but it's being used like

menu_layout(menu, &SCREEN_REGION);

all over the place. Does 'referenced' mean something else than what I think it does?

No. What's happening is that a header file is causing SCREEN_REGION to be defined as static in every single file, even those which don't make use of it. You'll only be getting warnings from the files which don't reference SCREEN_REGION but nevertheless include the ui.h (I think) file.

[Pete Mack]

To be fair its last release was in February 2009 so it wasn't exactly obvious to me that it was obsolete.

I had no idea. I wonder what keeps it alive? Anyway, those warnings are wrong.

Really, gcc (aka MINGW) and Visual Studio are the industry standards, with Sun and HP still around for special-purpose code. (lcc is still out there for a light-weight portable compiler, but since it doesn't include C++, it's kind of obsolete.)

[zaimoni]

Originally Posted by Pete Mack

I had no idea. I wonder what keeps it alive?

The Watcom compiler was open-sourced a few years back; it's properly OpenWatcom now.

[PaulBlay]

Originally Posted by zaimoni

The Watcom compiler was open-sourced a few years back; it's properly OpenWatcom now.

Hence

I'm trying to get Open Watcom to work for me at the moment.

Incidentally it is apparently possible to work around the 'same filename different directory' problem, but it's not very user friendly so I'm leaving it for now.

VC++ has its own quirks (angband.ico has to be in the same directory as angband.rc, for instance).