home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!cs.utexas.edu!uwm.edu!ogicse!news.u.washington.edu!serval!hlu
- From: hlu@eecs.wsu.edu (H.J. Lu)
- Newsgroups: comp.unix.bsd
- Subject: Re: [386bsd] GNU malloc in favor of BSD malloc in libc - shall we vote?
- Message-ID: <1993Jan1.001332.15123@serval.net.wsu.edu>
- Date: 1 Jan 93 00:13:32 GMT
- Article-I.D.: serval.1993Jan1.001332.15123
- References: <JKH.92Dec31154004@whisker.lotus.ie> <1hvu79INNjqq@ftp.UU.NET>
- Sender: news@serval.net.wsu.edu (USENET News System)
- Organization: School of EECS, Washington State University
- Lines: 18
-
- In article <1hvu79INNjqq@ftp.UU.NET>, sef@Kithrup.COM (Sean Eric Fagan) writes:
- |> "comp" is not a valid distribution. By putting "Distribution: comp" in your
- |> header, you have caused or allowed a growing number of sites around the
- |> world to drop your article on the floor. If you don't care whether or not
- |> people see your article, please feel free to continue using invalid dis-
- |> tributions.
- |>
- |> In article <JKH.92Dec31154004@whisker.lotus.ie> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes:
- |> >I say we petition Bill to use GNU malloc in preference.
- |>
- |> GNU malloc is copylefted. Using it in a library means that every program
- |> compiled using that library is copylefted. That is almost certainly the
- |> reason why it is not used, and I cannot fault anyone for that.
-
- Is that under GLGPL? Another `feature' in GNU malloc is malloc (0) returns
- NULL.
-
- H.J.
-