From owner-cvs-include Tue Nov 15 05:42:26 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id FAA03667 for cvs-include-outgoing; Tue, 15 Nov 1994 05:42:26 -0800 Received: (from ache@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id FAA03657; Tue, 15 Nov 1994 05:42:22 -0800 Date: Tue, 15 Nov 1994 05:42:22 -0800 From: "Andrew A. Chernov" Message-Id: <199411151342.FAA03657@freefall.cdrom.com> To: CVS-commiters, cvs-include Subject: cvs commit: src/include malloc.h Makefile Sender: cvs-include-owner@FreeBSD.org Precedence: bulk ache 94/11/15 05:42:21 Modified: include Makefile Added: include malloc.h Log: Add malloc.h for better SYSV/Linux compatibility like most providers (like SUN f.e.) does. malloc.h have comment about its SYSVism From owner-cvs-include Tue Nov 15 08:49:39 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id IAA09079 for cvs-include-outgoing; Tue, 15 Nov 1994 08:49:39 -0800 Received: from bsd.coe.montana.edu (bsd.coe.montana.edu [153.90.192.29]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id IAA09073; Tue, 15 Nov 1994 08:49:33 -0800 Received: (nate@localhost) by bsd.coe.montana.edu (8.6.8/8.3) id JAA09195; Tue, 15 Nov 1994 09:53:38 -0700 Date: Tue, 15 Nov 1994 09:53:38 -0700 From: Nate Williams Message-Id: <199411151653.JAA09195@bsd.coe.montana.edu> In-Reply-To: "Andrew A. Chernov" "cvs commit: src/include malloc.h Makefile" (Nov 15, 5:42am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Andrew A. Chernov" , CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com Subject: Re: cvs commit: src/include malloc.h Makefile Sender: cvs-include-owner@FreeBSD.org Precedence: bulk > ache 94/11/15 05:42:21 > > Modified: include Makefile > Added: include malloc.h > Log: > Add malloc.h for better SYSV/Linux compatibility like most > providers (like SUN f.e.) does. > malloc.h have comment about its SYSVism Umm, in your reply to me, you said you were going to fix the ports that require it. If you are just going to add 'malloc.h', why don't you add the libmalloc stuff from 1.1.5? From owner-cvs-include Tue Nov 15 09:02:32 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id JAA09248 for cvs-include-outgoing; Tue, 15 Nov 1994 09:02:32 -0800 Received: from precipice.Shockwave.COM (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id JAA09242; Tue, 15 Nov 1994 09:02:26 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.Shockwave.COM (8.6.9/8.6.9) with SMTP id JAA02575; Tue, 15 Nov 1994 09:01:17 -0800 Message-Id: <199411151701.JAA02575@precipice.Shockwave.COM> To: Nate Williams cc: "Andrew A. Chernov" , CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com Subject: Re: cvs commit: src/include malloc.h Makefile In-reply-to: Your message of "Tue, 15 Nov 1994 09:53:38 MST." <199411151653.JAA09195@bsd.coe.montana.edu> Date: Tue, 15 Nov 1994 09:01:16 -0800 From: Paul Traina Sender: cvs-include-owner@FreeBSD.org Precedence: bulk Why would we want the system5 fatmalloc? Why do we want malloc() at all? Did our name change to FreeUnivel? From: Nate Williams Subject: Re: cvs commit: src/include malloc.h Makefile > ache 94/11/15 05:42:21 > > Modified: include Makefile > Added: include malloc.h > Log: > Add malloc.h for better SYSV/Linux compatibility like most > providers (like SUN f.e.) does. > malloc.h have comment about its SYSVism Umm, in your reply to me, you said you were going to fix the ports that require it. If you are just going to add 'malloc.h', why don't you add the libmalloc stuff from 1.1.5? From owner-cvs-include Tue Nov 15 09:06:21 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id JAA09265 for cvs-include-outgoing; Tue, 15 Nov 1994 09:06:21 -0800 Received: from bsd.coe.montana.edu (bsd.coe.montana.edu [153.90.192.29]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id JAA09259; Tue, 15 Nov 1994 09:06:14 -0800 Received: (nate@localhost) by bsd.coe.montana.edu (8.6.8/8.3) id KAA09414; Tue, 15 Nov 1994 10:10:15 -0700 Date: Tue, 15 Nov 1994 10:10:15 -0700 From: Nate Williams Message-Id: <199411151710.KAA09414@bsd.coe.montana.edu> In-Reply-To: Paul Traina "Re: cvs commit: src/include malloc.h Makefile" (Nov 15, 9:01am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Paul Traina Subject: Re: cvs commit: src/include malloc.h Makefile Cc: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com Sender: cvs-include-owner@FreeBSD.org Precedence: bulk > Why would we want the system5 fatmalloc? Why do we want malloc() at all? Umm, do you have *any* idea what you are talking about? The libmalloc() supplied in 1.1.5 is Mark Moraes replacement malloc() that is *much* more frugal on memory use with only a slight performance hit. It was my intent to replace the version in 2.X with this version, but due to lack of time and testing on my part I didn't get time to do it. By adding it to 2.X we have it in public where it *may* get more testing than by sitting doing nothing. It is leaner/meaner than the stock version and not fat in the least bit. The second question seems rather silly to me. Gee, I don't know why we want malloc(), maybe since the ability to do dynamic memory in programs is generally considered a good feature? Nate From owner-cvs-include Tue Nov 15 09:18:29 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id JAA09375 for cvs-include-outgoing; Tue, 15 Nov 1994 09:18:29 -0800 Received: from precipice.Shockwave.COM (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id JAA09369; Tue, 15 Nov 1994 09:18:23 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.Shockwave.COM (8.6.9/8.6.9) with SMTP id JAA02754; Tue, 15 Nov 1994 09:17:18 -0800 Message-Id: <199411151717.JAA02754@precipice.Shockwave.COM> To: Nate Williams cc: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com Subject: Re: cvs commit: src/include malloc.h Makefile In-reply-to: Your message of "Tue, 15 Nov 1994 10:10:15 MST." <199411151710.KAA09414@bsd.coe.montana.edu> Date: Tue, 15 Nov 1994 09:17:18 -0800 From: Paul Traina Sender: cvs-include-owner@FreeBSD.org Precedence: bulk From: Nate Williams Subject: Re: cvs commit: src/include malloc.h Makefile > Why would we want the system5 fatmalloc? Why do we want malloc() at all? Umm, do you have *any* idea what you are talking about? The libmalloc() No, I didn't. supplied in 1.1.5 is Mark Moraes replacement malloc() that is *much* more frugal on memory use with only a slight performance hit. It was my intent to replace the version in 2.X with this version, but due to lack of time and testing on my part I didn't get time to do it. By adding it to 2.X we have it in public where it *may* get more testing than by sitting doing nothing. It is leaner/meaner than the stock version and not fat in the least bit. The second question seems rather silly to me. Gee, I don't know why we want malloc(), maybe since the ability to do dynamic memory in programs is generally considered a good feature? Yes, indeed. However, the idea as I understand here is that we're including a /usr/include/malloc.h for SystemV compatibility. Searching back through my ugly USG memory, malloc.h is _intended_ to only be included if you're linking against the SystemV libmalloc, you weren't SUPPOSED to use it unless you were doing so, because all the diags weren't there and the internal structures between the dynamic allocation code in libc and libmalloc were completely different. The USG libmalloc was the fast-but-bloated-and-stupid malloc, while the libc malloc was the one normal mortals would use. One of the biggest problems I have with malloc.h is that there is a conflict between declaring malloc as returning type char * and void *. You really want malloc to be defined as returning void *, and that's how it SHOULD be defined in malloc.h, but almost everyone defines it as char * for stupid historical reasons. If you define it one way, and someone else does it the other way, you generate an error or a warning. If you don't define it at all, the worse you get is a warning, and most of the time you don't get that at all because people seem to insist on casting the output of malloc (more historical stupidity from the days before void * existed). From owner-cvs-include Tue Nov 15 09:19:18 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id JAA09390 for cvs-include-outgoing; Tue, 15 Nov 1994 09:19:18 -0800 Received: from precipice.Shockwave.COM (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id JAA09383; Tue, 15 Nov 1994 09:19:15 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.Shockwave.COM (8.6.9/8.6.9) with SMTP id JAA02781; Tue, 15 Nov 1994 09:18:10 -0800 Message-Id: <199411151718.JAA02781@precipice.Shockwave.COM> To: Nate Williams cc: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com Subject: Re: cvs commit: src/include malloc.h Makefile In-reply-to: Your message of "Tue, 15 Nov 1994 10:10:15 MST." <199411151710.KAA09414@bsd.coe.montana.edu> Date: Tue, 15 Nov 1994 09:18:10 -0800 From: Paul Traina Sender: cvs-include-owner@FreeBSD.org Precedence: bulk Oh, and sorry, that second question was supposed to be: Why do we want libmalloc.a at all... I claim feeblemindedness due to a bad case of the flu. From: Nate Williams Subject: Re: cvs commit: src/include malloc.h Makefile > Why would we want the system5 fatmalloc? Why do we want malloc() at all? Umm, do you have *any* idea what you are talking about? The libmalloc() supplied in 1.1.5 is Mark Moraes replacement malloc() that is *much* more frugal on memory use with only a slight performance hit. It was my intent to replace the version in 2.X with this version, but due to lack of time and testing on my part I didn't get time to do it. By adding it to 2.X we have it in public where it *may* get more testing than by sitting doing nothing. It is leaner/meaner than the stock version and not fat in the least bit. The second question seems rather silly to me. Gee, I don't know why we want malloc(), maybe since the ability to do dynamic memory in programs is generally considered a good feature? Nate From owner-cvs-include Tue Nov 15 09:23:52 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id JAA09435 for cvs-include-outgoing; Tue, 15 Nov 1994 09:23:52 -0800 Received: from bsd.coe.montana.edu (bsd.coe.montana.edu [153.90.192.29]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id JAA09425; Tue, 15 Nov 1994 09:23:46 -0800 Received: (nate@localhost) by bsd.coe.montana.edu (8.6.8/8.3) id KAA09547; Tue, 15 Nov 1994 10:27:19 -0700 Date: Tue, 15 Nov 1994 10:27:19 -0700 From: Nate Williams Message-Id: <199411151727.KAA09547@bsd.coe.montana.edu> In-Reply-To: Paul Traina "Re: cvs commit: src/include malloc.h Makefile" (Nov 15, 9:17am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Paul Traina Subject: Re: cvs commit: src/include malloc.h Makefile Cc: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com Sender: cvs-include-owner@FreeBSD.org Precedence: bulk [ Having /usr/include/malloc.h ] > Yes, indeed. However, the idea as I understand here is that we're including a > /usr/include/malloc.h for SystemV compatibility. Yeah, that's a bad thing. However, IF andrew is going to put it in, why not add some additional functionality besides the include file. I don't necessarily agree that it should go in /usr/include, but *if* it is, let's go all the way and get a decent malloc implementation at the same time. It is actually a very nice package, providing debugging support and other helpful features. > libc and libmalloc were completely different. The USG libmalloc was the > fast-but-bloated-and-stupid malloc, while the libc malloc was the one normal > mortals would use. Ahh, but in our case (if we added libmalloc), the opposite would be true. We have a fast-but-bloated malloc in libc, while the version in libmalloc is not-as-fast-and-not-so-bloated. ;) > If you don't define it at all, the worse you get is a warning, Except that many (mostly Linux) programs include , and compiles simply fail. The decision was made (apparently) to create a dummy malloc.h which would allow compiles to work, even though the offending programs shouldn't use malloc.h. Nate From owner-cvs-include Tue Nov 15 10:33:13 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id KAA10192 for cvs-include-outgoing; Tue, 15 Nov 1994 10:33:13 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.cdrom.com (8.6.8/8.6.6) with SMTP id KAA10184; Tue, 15 Nov 1994 10:32:57 -0800 Received: by sovcom.kiae.su id AA02114 (5.65.kiae-2 ); Tue, 15 Nov 1994 21:30:21 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id VAA00982; Tue, 15 Nov 1994 21:23:37 +0300 To: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com, Nate Williams References: <199411151653.JAA09195@bsd.coe.montana.edu> In-Reply-To: <199411151653.JAA09195@bsd.coe.montana.edu>; from Nate Williams at Tue, 15 Nov 1994 09:53:38 -0700 Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 15 Nov 1994 21:23:36 +0300 X-Mailer: Mail/@ [v2.29 FreeBSD] From: "Andrew A. Chernov, Black Mage" X-Class: Fast Subject: Re: cvs commit: src/include malloc.h Makefile Lines: 32 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1372 Sender: cvs-include-owner@FreeBSD.org Precedence: bulk In message <199411151653.JAA09195@bsd.coe.montana.edu> Nate Williams writes: >> ache 94/11/15 05:42:21 >> >> Modified: include Makefile >> Added: include malloc.h >> Log: >> Add malloc.h for better SYSV/Linux compatibility like most >> providers (like SUN f.e.) does. >> malloc.h have comment about its SYSVism >Umm, in your reply to me, you said you were going to fix the ports >that require it. If you are just going to add 'malloc.h', why >don't you add the libmalloc stuff from 1.1.5? In early days I think, that it is easy to fix all ports, but now I really tired to do that way, it is why I include malloc.h. Moreover, all commercial vendors include it. SYSV is de-facto standard and we can't teach all world to do it another way. I don't need libmalloc for Linux/SYSV ports, just malloc.h only. I also don't want to add -lmalloc to each such port, if malloc.h included in libmalloc. If you are 100% shure that libmalloc is beter than standard malloc, just replace malloc in _standard_ libc and add additional things into malloc.h. -- Andrew A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: -- temp down -- : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-cvs-include Tue Nov 15 10:33:48 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id KAA10210 for cvs-include-outgoing; Tue, 15 Nov 1994 10:33:48 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.cdrom.com (8.6.8/8.6.6) with SMTP id KAA10203; Tue, 15 Nov 1994 10:33:38 -0800 Received: by sovcom.kiae.su id AA02215 (5.65.kiae-2 ); Tue, 15 Nov 1994 21:31:04 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id VAA01008; Tue, 15 Nov 1994 21:26:47 +0300 To: Nate Williams , Paul Traina Cc: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com References: <199411151701.JAA02575@precipice.Shockwave.COM> In-Reply-To: <199411151701.JAA02575@precipice.Shockwave.COM>; from Paul Traina at Tue, 15 Nov 1994 09:01:16 -0800 Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 15 Nov 1994 21:26:46 +0300 X-Mailer: Mail/@ [v2.29 FreeBSD] From: "Andrew A. Chernov, Black Mage" X-Class: Fast Subject: Re: cvs commit: src/include malloc.h Makefile Lines: 19 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 745 Sender: cvs-include-owner@FreeBSD.org Precedence: bulk In message <199411151701.JAA02575@precipice.Shockwave.COM> Paul Traina writes: >Why would we want the system5 fatmalloc? Why do we want malloc() at all? We don't want fatmalloc. All SYSV/Linux pgms which use simple _malloc_ include this file. >Did our name change to FreeUnivel? We already have some SYSVish things like strings.h->string.h All SYSVish headers (malloc.h,values.h) now have comment in first line which tell users don't use it. -- Andrew A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: -- temp down -- : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-cvs-include Tue Nov 15 10:43:47 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id KAA10337 for cvs-include-outgoing; Tue, 15 Nov 1994 10:43:47 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.cdrom.com (8.6.8/8.6.6) with SMTP id KAA10326; Tue, 15 Nov 1994 10:43:31 -0800 Received: by sovcom.kiae.su id AA02591 (5.65.kiae-2 ); Tue, 15 Nov 1994 21:36:24 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id VAA01059; Tue, 15 Nov 1994 21:31:34 +0300 To: Nate Williams , Paul Traina Cc: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com References: <199411151727.KAA09547@bsd.coe.montana.edu> In-Reply-To: <199411151727.KAA09547@bsd.coe.montana.edu>; from Nate Williams at Tue, 15 Nov 1994 10:27:19 -0700 Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 15 Nov 1994 21:31:33 +0300 X-Mailer: Mail/@ [v2.29 FreeBSD] From: "Andrew A. Chernov, Black Mage" X-Class: Fast Subject: Re: cvs commit: src/include malloc.h Makefile Lines: 17 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 668 Sender: cvs-include-owner@FreeBSD.org Precedence: bulk In message <199411151727.KAA09547@bsd.coe.montana.edu> Nate Williams writes: >Except that many (mostly Linux) programs include , and >compiles simply fail. The decision was made (apparently) to create a >dummy malloc.h which would allow compiles to work, even though the >offending programs shouldn't use malloc.h. Yes, I just want to say the same thing. -- Andrew A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: -- temp down -- : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-cvs-include Tue Nov 15 10:44:04 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id KAA10356 for cvs-include-outgoing; Tue, 15 Nov 1994 10:44:04 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.cdrom.com (8.6.8/8.6.6) with SMTP id KAA10342; Tue, 15 Nov 1994 10:43:50 -0800 Received: by sovcom.kiae.su id AA02571 (5.65.kiae-2 ); Tue, 15 Nov 1994 21:36:09 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id VAA01045; Tue, 15 Nov 1994 21:29:52 +0300 To: Nate Williams , Paul Traina Cc: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com References: <199411151717.JAA02754@precipice.Shockwave.COM> In-Reply-To: <199411151717.JAA02754@precipice.Shockwave.COM>; from Paul Traina at Tue, 15 Nov 1994 09:17:18 -0800 Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 15 Nov 1994 21:29:52 +0300 X-Mailer: Mail/@ [v2.29 FreeBSD] From: "Andrew A. Chernov, Black Mage" X-Class: Fast Subject: Re: cvs commit: src/include malloc.h Makefile Lines: 27 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1424 Sender: cvs-include-owner@FreeBSD.org Precedence: bulk In message <199411151717.JAA02754@precipice.Shockwave.COM> Paul Traina writes: >Searching back through my ugly USG memory, malloc.h is _intended_ to only >be included if you're linking against the SystemV libmalloc, you weren't >SUPPOSED to use it unless you were doing so, because all the diags weren't >there and the internal structures between the dynamic allocation code in >libc and libmalloc were completely different. The USG libmalloc was the >fast-but-bloated-and-stupid malloc, while the libc malloc was the one normal >mortals would use. It is untrue, it needed for just simple malloc(), check Linux box f.e. >One of the biggest problems I have with malloc.h is that there is a conflict >between declaring malloc as returning type char * and void *. You really want >malloc to be defined as returning void *, and that's how it SHOULD be defined >in malloc.h, but almost everyone defines it as char * for stupid historical >reasons. If you define it one way, and someone else does it the other way, >you generate an error or a warning. There is no conflicts, just the same prototypes from stdlib.h copied. -- Andrew A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: -- temp down -- : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-cvs-include Tue Nov 15 15:05:04 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id PAA13882 for cvs-include-outgoing; Tue, 15 Nov 1994 15:05:04 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.8/8.6.6) with SMTP id PAA13873; Tue, 15 Nov 1994 15:04:49 -0800 Received: by halloran-eldar.lcs.mit.edu; id AA07442; Tue, 15 Nov 1994 18:04:29 -0500 Date: Tue, 15 Nov 1994 18:04:29 -0500 From: Garrett Wollman Message-Id: <9411152304.AA07442@halloran-eldar.lcs.mit.edu> To: "Andrew A. Chernov, Black Mage" Cc: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com Subject: Re: cvs commit: src/include malloc.h Makefile In-Reply-To: References: <199411151653.JAA09195@bsd.coe.montana.edu> Sender: cvs-include-owner@FreeBSD.org Precedence: bulk < said: > Moreover, all commercial vendors include it. SYSV is de-facto standard > and we can't teach all world to do it another way. Repeat after me. FreeBSD != SysV. FreeBSD != SysV. It is not even a remote goal of FreeBSD to emulate SysV brain-damage. FreeBSD != SysV. (Now, those one or two things that SysV actually got right, those might be worth emulating. This isn't one of them. Unfortunately, this particular bit of brain-damage is contagious, as it infected all the MS-DOG C compilers quite early on...) -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-cvs-include Tue Nov 15 17:17:34 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id RAA16948 for cvs-include-outgoing; Tue, 15 Nov 1994 17:17:34 -0800 Received: from bsd.coe.montana.edu (bsd.coe.montana.edu [153.90.192.29]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id RAA16939; Tue, 15 Nov 1994 17:17:24 -0800 Received: (nate@localhost) by bsd.coe.montana.edu (8.6.8/8.3) id SAA10548; Tue, 15 Nov 1994 18:21:15 -0700 Date: Tue, 15 Nov 1994 18:21:15 -0700 From: Nate Williams Message-Id: <199411160121.SAA10548@bsd.coe.montana.edu> In-Reply-To: "Andrew A. Chernov, Black Mage" "Re: cvs commit: src/include malloc.h Makefile" (Nov 15, 9:23pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Andrew A. Chernov, Black Mage" , CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com Subject: Re: cvs commit: src/include malloc.h Makefile Sender: cvs-include-owner@FreeBSD.org Precedence: bulk > I don't need libmalloc for Linux/SYSV ports, just malloc.h only. > I also don't want to add -lmalloc to each such port, if > malloc.h included in libmalloc. If you are 100% shure that > libmalloc is beter than standard malloc, just replace malloc > in _standard_ libc and add additional things into malloc.h. I'm not 100% sure that it's bug-free. That's the problem. However, I'm 100% that it's more frugal with memory and almost as fast. Nate From owner-cvs-include Wed Nov 16 03:43:03 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id DAA21423 for cvs-include-outgoing; Wed, 16 Nov 1994 03:43:03 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.cdrom.com (8.6.8/8.6.6) with SMTP id DAA21342; Wed, 16 Nov 1994 03:41:28 -0800 Received: by sovcom.kiae.su id AA16772 (5.65.kiae-2 ); Wed, 16 Nov 1994 14:34:58 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id OAA00881; Wed, 16 Nov 1994 14:23:16 +0300 To: Garrett Wollman Cc: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com References: <199411151653.JAA09195@bsd.coe.montana.edu> <9411152304.AA07442@halloran-eldar.lcs.mit.edu> In-Reply-To: <9411152304.AA07442@halloran-eldar.lcs.mit.edu>; from Garrett Wollman at Tue, 15 Nov 1994 18:04:29 -0500 Message-Id: Organization: Olahm Ha-Yetzirah Date: Wed, 16 Nov 1994 14:23:16 +0300 X-Mailer: Mail/@ [v2.29 FreeBSD] From: "Andrew A. Chernov, Black Mage" X-Class: Fast Subject: Re: cvs commit: src/include malloc.h Makefile Lines: 31 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1547 Sender: cvs-include-owner@FreeBSD.org Precedence: bulk In message <9411152304.AA07442@halloran-eldar.lcs.mit.edu> Garrett Wollman writes: >< said: >> Moreover, all commercial vendors include it. SYSV is de-facto standard >> and we can't teach all world to do it another way. >Repeat after me. FreeBSD != SysV. FreeBSD != SysV. It is not even a >remote goal of FreeBSD to emulate SysV brain-damage. FreeBSD != SysV. 1) I don't plan _emulate_ SysV with this change, only save porters work time. 2) We already _emulate_ SysV (IBCS2 stuff), so FreeBSD almost == SysV :-) >(Now, those one or two things that SysV actually got right, those >might be worth emulating. This isn't one of them. Unfortunately, >this particular bit of brain-damage is contagious, as it infected all >the MS-DOG C compilers quite early on...) That I mean when say that this infection is de-facto standard. All commecrial vendors and even MSDOS C Compilers have this file. We can have different emotions about this file, but we can't negate its existance. I was agree with you until I done several ports myself and really tired edit every C file to undef this file. If you try to port few Linux things yourself, you understand me :-) -- Andrew A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: -- temp down -- : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-cvs-include Wed Nov 16 04:35:59 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id EAA27165 for cvs-include-outgoing; Wed, 16 Nov 1994 04:35:59 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id EAA27139; Wed, 16 Nov 1994 04:35:35 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id XAA17710; Wed, 16 Nov 1994 23:31:03 +1100 Date: Wed, 16 Nov 1994 23:31:03 +1100 From: Bruce Evans Message-Id: <199411161231.XAA17710@godzilla.zeta.org.au> To: ache@astral.msk.su, wollman@halloran-eldar.lcs.mit.edu Subject: Re: cvs commit: src/include malloc.h Makefile Cc: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com Sender: cvs-include-owner@FreeBSD.org Precedence: bulk >>might be worth emulating. This isn't one of them. Unfortunately, >>this particular bit of brain-damage is contagious, as it infected all >>the MS-DOG C compilers quite early on...) >That I mean when say that this infection is de-facto standard. All >commecrial vendors and even MSDOS C Compilers have this file. It isn't in Turbo C 1.0 (1987). It isn't in Turbo C++ 1.0 (1990). >If you try to port few Linux things yourself, you understand me :-) Isn't Linux supposed to be a POSIXish system? :-) Bruce From owner-cvs-include Wed Nov 16 07:22:17 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id HAA12964 for cvs-include-outgoing; Wed, 16 Nov 1994 07:22:17 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.cdrom.com (8.6.8/8.6.6) with SMTP id HAA12925; Wed, 16 Nov 1994 07:22:00 -0800 Received: by sovcom.kiae.su id AA06579 (5.65.kiae-2 ); Wed, 16 Nov 1994 18:15:35 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id RAA01513; Wed, 16 Nov 1994 17:55:00 +0300 To: Bruce Evans , wollman@halloran-eldar.lcs.mit.edu Cc: CVS-commiters@freefall.cdrom.com, cvs-include@freefall.cdrom.com References: <199411161231.XAA17710@godzilla.zeta.org.au> In-Reply-To: <199411161231.XAA17710@godzilla.zeta.org.au>; from Bruce Evans at Wed, 16 Nov 1994 23:31:03 +1100 Message-Id: Organization: Olahm Ha-Yetzirah Date: Wed, 16 Nov 1994 17:55:00 +0300 X-Mailer: Mail/@ [v2.29 FreeBSD] From: "Andrew A. Chernov, Black Mage" X-Class: Fast Subject: Re: cvs commit: src/include malloc.h Makefile Lines: 19 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 842 Sender: cvs-include-owner@FreeBSD.org Precedence: bulk In message <199411161231.XAA17710@godzilla.zeta.org.au> Bruce Evans writes: >>>might be worth emulating. This isn't one of them. Unfortunately, >>>this particular bit of brain-damage is contagious, as it infected all >>>the MS-DOG C compilers quite early on...) >>That I mean when say that this infection is de-facto standard. All >>commecrial vendors and even MSDOS C Compilers have this file. >It isn't in Turbo C 1.0 (1987). It isn't in Turbo C++ 1.0 (1990). It is at least in Borland C 3.0 and Microsoft C 6. Turbo C is obsolete now. -- Andrew A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: -- temp down -- : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-cvs-include Thu Nov 17 03:04:57 1994 Return-Path: cvs-include-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id DAA18383 for cvs-include-outgoing; Thu, 17 Nov 1994 03:04:57 -0800 Received: (from ache@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id DAA18370; Thu, 17 Nov 1994 03:04:51 -0800 Date: Thu, 17 Nov 1994 03:04:51 -0800 From: "Andrew A. Chernov" Message-Id: <199411171104.DAA18370@freefall.cdrom.com> To: CVS-commiters, cvs-include Subject: cvs commit: src/include malloc.h Sender: cvs-include-owner@FreeBSD.org Precedence: bulk ache 94/11/17 03:04:50 Modified: include malloc.h Log: By Bruce and Joerg suggestions and by looking into June version of NetBSD simple #include into malloc.h Put #warning that this file is obsoleted ( by Joerg suggestion)