From 442d21a78026ec83de4495a78d8e36aa39fa95b6 Mon Sep 17 00:00:00 2001 From: Bardur Arantsson Date: Thu, 26 Jun 2014 20:45:08 +0200 Subject: Remove pointless comment in types.h --- src/types.h | 24 ------------------------ 1 file changed, 24 deletions(-) (limited to 'src') diff --git a/src/types.h b/src/types.h index b629c0e3..6a1f8536 100644 --- a/src/types.h +++ b/src/types.h @@ -51,30 +51,6 @@ /* * Template file header information (see "init.c"). 16 bytes. - * - * Note that the sizes of many of the "arrays" are between 32768 and - * 65535, and so we must use "unsigned" values to hold the "sizes" of - * these arrays below. Normally, I try to avoid using unsigned values, - * since they can cause all sorts of bizarre problems, but I have no - * choice here, at least, until the "race" array is split into "normal" - * and "unique" monsters, which may or may not actually help. - * - * Note that, on some machines, for example, the Macintosh, the standard - * "read()" and "write()" functions cannot handle more than 32767 bytes - * at one time, so we need replacement functions, see "util.c" for details. - * - * Note that, on some machines, for example, the Macintosh, the standard - * "malloc()" function cannot handle more than 32767 bytes at one time, - * but we may assume that the "ralloc()" function can handle up to 65535 - * butes at one time. We should not, however, assume that the "ralloc()" - * function can handle more than 65536 bytes at a time, since this might - * result in segmentation problems on certain older machines, and in fact, - * we should not assume that it can handle exactly 65536 bytes at a time, - * since the internal functions may use an unsigned short to specify size. - * - * In general, these problems occur only on machines (such as most personal - * computers) which use 2 byte "int" values, and which use "int" for the - * arguments to the relevent functions. */ typedef struct header header; -- cgit v1.2.3