Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!apple!julius.cs.uiuc.edu!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn From: gwyn@smoke.BRL.MIL (Doug Gwyn) Newsgroups: comp.unix.questions Subject: Re: Compiling tinymud2 under HP-UX Message-ID: <13836@smoke.BRL.MIL> Date: 12 Sep 90 20:16:20 GMT References: <138@wgate.UUCP> <22531:Sep1119:36:4090@kramden.acf.nyu.edu> Organization: U.S. Army Ballistic Research Laboratory, APG, MD. Lines: 17 In article <22531:Sep1119:36:4090@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes: >getdtablesize returns the maximum number of file descriptors; try >replacing any use of it by NOFILE. (Obligatory swipe at C: You can't do >this with a macro.) Sure you can, assuming that the application does not contain an explicit declaration like extern int getdtablesize(); which would be a pretty safe assumption for many BSD-based applications. #define getdtablesize() NOFILE /* assuming is being #included */ >bcopy(src,dst,len) is (basically) the same as memcpy(dst,src,len). Except for the types of the function return and also the "len" argument. Also, a few uses of bcopy() assume memmove()-like behavior for overlapping source and destination, in which case memcpy() may not be suitable.