X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f Subject: Re: Basic Use of malloc X-Old-trace: nets3.rz.RWTH-Aachen.DE 1063021395 17096 137.226.32.75 (8 Sep 2003 11:43:15 GMT) Approved: clc AT plethora DOT net Content-Transfer-encoding: 7BIT References: From: Hans-Bernhard Broeker Organization: Aachen University of Technology (RWTH) Followup-To: comp.os.msdos.djgpp X-Old-complaints-to: abuse AT rwth-aachen DOT de Newsgroups: comp.lang.c.moderated,comp.os.msdos.djgpp Originator: broeker@ Message-ID: Originator: clcm AT plethora DOT net (Comp Lang C'Moderated) Date: 10 Sep 2003 21:56:22 GMT Lines: 21 NNTP-Posting-Host: 4bfd53c5.news.plethora.net X-Trace: 1063230982 gemini.plethora.net 1095 clcm AT 205 DOT 166 DOT 146 DOT 1 X-Complaints-To: abuse AT plethora DOT net To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com [Note: X-post and F'up2] kentinjapan wrote: [...] > I seem to be able to make much larger arrays using malloc then I could > by simply declaring an array as I did in my previous example. Is this > to be expected? I am using DJGPP and I was only able to declare a char > array of around 500,000 previously and now using the method above with > malloc I was able to create and initialize a char array of > 500,000,000. That difference was not really caused by using malloc instead of arrays, but rather by your failure to read the DJGPP FAQ or ask the right people about that limitation. I'm redirecting this to the place where you'll find those people. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain. -- comp.lang.c.moderated - moderation address: clcm AT plethora DOT net