From -7554798742676992363 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1149ec,f5b50f79e3b33c8d X-Google-Attributes: gid1149ec,public X-Google-Thread: f78e5,c0143c56db298752 X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 1994-09-17 02:19:40 PST Newsgroups: comp.std.c,comp.std.c++ Path: bga.com!news.sprintlink.net!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!solaris.cc.vt.edu!uunet!munnari.oz.au!cs.mu.OZ.AU!munta.cs.mu.OZ.AU!fjh From: fjh@munta.cs.mu.OZ.AU (Fergus Henderson) Subject: Re: malloc calls FROM the standard library (was: Re: Question on 5.2.3.) Message-ID: <9425919.22386@mulga.cs.mu.OZ.AU> Sender: news@cs.mu.OZ.AU Organization: Computer Science, University of Melbourne, Australia References: <1994Sep10.033223.23015@nlm.nih.gov> <352ps8$j32@reuter.cse.ogi.edu> <354jbs$54q@ritz.cec.wustl.edu> Date: Fri, 16 Sep 1994 09:25:16 GMT Lines: 11 Xref: bga.com comp.std.c:2972 comp.std.c++:4305 jaf3@ritz.cec.wustl.edu (John Andrew Fingerhut) writes: >I don't particularly mind when things don't work early >in the development cycle....it's when they blow up after the customer has >it that really causes a problem. ... or when things work fine until you try to port the program (e.g. to the next version of the operating system.) -- Fergus Henderson - fjh@munta.cs.mu.oz.au