From owner-freebsd-current Sat Apr 25 14:52:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23267 for freebsd-current-outgoing; Sat, 25 Apr 1998 14:52:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23262 for ; Sat, 25 Apr 1998 14:52:08 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id RAA16872; Sat, 25 Apr 1998 17:52:01 -0400 (EDT) (envelope-from wollman) Date: Sat, 25 Apr 1998 17:52:01 -0400 (EDT) From: Garrett Wollman Message-Id: <199804252152.RAA16872@khavrinen.lcs.mit.edu> To: Tom Cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: sysctl from Linux (*envy*) In-Reply-To: References: <19980424224346.35645@follo.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I'm not aware of any program that does that. I'm not aware why any > application programmer would even think malloc'ing they aren't using is a > good idea. It just doesn't make sense on any modern VM system. You're right---there are no such programs that do that. What you do have, instead, is dusty FORTRAN programs which allocate huge BSS sections with arrays declared to their maximum conceivable dimensions, since FORTRAN-66 didn't have dynamic allocation. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message