Add putmixed() to the window port. It allows map symbols to be included in the string by encoding them in a unique fashion. This was done because Unicode symbols, for instance, could be longer than the size of a char. The encoding of the map symbols in this patch is done by prefixing a glyph value with \GXXXX, where XXXX is a random value for the current game. The reason for the random prefix is to minimize the possibility that a player can trigger the escape sequence processing within text under their control (dog names, etc.) the way they could if the sequence was fixed in the source code. The random prefix remains the same throughout the lifetime of a game because message window strings are saved in the save file. (There was actually a bug present because of the embedded character even before the recent symbol changes, because if someone was using a different set of characters between games, the saved messages would reflect the original characters, rather than the current. That bug was introduced with the ability to save messages to the savefile.) A window port does not have to supply an XXX_putmixed() routine, it can use genl_putmixed() which uses the old behavior of embedding the sequence as a character within the string and calling putstr(). genl_putmixed() takes care of the decoding of the escape sequence. This also #ifdef's out code in pager.c for converting a glyph to a character, and uses mapglyph() to do that instead. Does anyone see a problem with doing that through mapglyph instead of repeating similar code within pager.c?
Jan 2002 The MPW compilers are now supported again. Support for 68k has been discontinued due to a lack of a debugging system for 68k binaries. Note that the tiled MacOS X port uses the Qt windowport and the UNIX build system, not this windowport code. 26 Nov, 1999 NetHack 3.3.0 was built with Metrowerk's Pro 4 compiler on a PPC system. We are still compiling with 68K alignment because we know it works. No one has checked lately if the PPC alignment bug still exists. 23 May, 1996 NetHack 3.2.1 was built with Metrowerk's DR8 compiler on a PPC system. The official 68K and PPC versions were compiled with 68K Alignment to share files. The 3.2.0 versions were compiled with PPC alignment, but it was discovered that the Metrowerks 68K compiler has a bug with PPC alignment and structures that can be aligned to a single byte. This bug _may_ be fixed in DR10, it is not fixed in DR9. Why bother with PPC alignment at all? Because the space saving from 68K alignment is small and the PowerPC version will run better. The 68K version was compiled with 4 byte ints using the far model. Only the Metrowerks compiler has been used to compile the code in a long time. It is _very_ likely that the other compilers, Think C and MPW C, will no longer be able to compile NetHack out of the box. They and their files have been moved to the "old" directory until such time that someone can compile with them.