On Sat, 2 Jun 2001, Peter Ajamian wrote:
>Found what is potentially a serious stock bug which would prevent
>CircleMUD from operating on a 16 bit platform:
What 16-bit platform that we support? The only one I can think of that
might qualify is Acorn's RiscOS. Maybe the Macintosh, depending on
processor. We don't support Windows 3.1 because the standard TCP/IP Winsock
isn't there.
>Of course the simple fix for this is to change experience from an int to
>a long, but wait, won't this break binary compatibility on 16 bit
>platforms? The short answer is "no". The reason? We never _had_ binary
>compatibilty for 16 bit platforms, CircleMUD was _always_ broken on 16
>bit platforms. This releases us from _any_ obligation to continue to
>support such non-existant binary-compatibility.
Actually, we can't do it because it would break 64-bit platforms.
32-bit 64-bit
char 1 1
short 2 2
int 4 4
long 4 8
long*2 8 8
So 'int' -> 'long' would increase it from 4 bytes to 8 bytes for 64-bit.
I know CircleMUD can compile on 64-bit, I'm not 100% sure of any 16-bit
off-hand.
--
George Greer
greerga@circlemud.org
--
+---------------------------------------------------------------+
| FAQ: http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
| Archives: http://post.queensu.ca/listserv/wwwarch/circle.html |
+---------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/05/01 PST