Article View: mod.std.unix
Article #65limits.h
From: Moderator, John Quarterman
Date: Sat, 16 Nov 1985 00:34
Date: Sat, 16 Nov 1985 00:34
21 lines
1534 bytes
1534 bytes
Date: Fri, 15 Nov 85 00:48:36 cst From: allegra!jpl (John P. Linderman) I agree that values like OPEN_MAX that may well vary among binary compatible machines should be determinable at execution time. It makes a lot of sense to have a routine that would look them up in the copy of limits.h on the runtime machine. If the file were missing (or otherwise unusable), default values could be compiled in from the copy of limits.h on the compile-time machine. This would leave us with sensible defaults, even on a bare-bones machine, and a high level of compatibility across binary compatible machines, regardless of the machine a source was compiled on. I don't imagine people will bury these lookups deep in nested loops, so efficiency shouldn't be much of an issue. A lookup that invoked cpp would be easy to write and would guarantee compatibility with compile-time lookups. John P. Linderman allegra!jpl Volume-Number: Volume 3, Number 20
Technical Details
Message-ID:
<3529@ut-sally.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!linus!gatech!seismo!ut-sally!std-unixShow Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site ut-sally.UUCP Path: arc1-ca.pugleaf.net!utzoo!linus!gatech!seismo!ut-sally!std-unix From: std-unix@ut-sally.UUCP (Moderator, John Quarterman) Newsgroups: mod.std.unix Subject: limits.h Message-ID: <3529@ut-sally.UUCP> Date: Fri, 15-Nov-85 19:34:39 EST Article-I.D.: ut-sally.3529 Posted: Fri Nov 15 19:34:39 1985 Date-Received: Sat, 16-Nov-85 03:57:16 EST Organization: IEEE/P1003 Portable Operating System Environment Committee Lines: 21 Approved: jsq@ut-sally.UUCP