From: Erik Max Francis <max AT alcyone DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: How big can I make my array?
Date: Fri, 12 Jun 1998 19:01:40 -0700
Organization: Alcyone Systems
Lines: 22
Message-ID: <3581DD84.6D6C891D@alcyone.com>
References: <MPG DOT fe223cb1cc75732989717 AT news DOT virgin DOT net> <3578C43D DOT F4DDB90 AT cs DOT com> <MPG DOT fe3efebb95c6032989725 AT news DOT virgin DOT net> <357AB3E4 DOT 316B4ED2 AT cs DOT com> <357c0c3a DOT 24494159 AT news DOT Austria DOT EU DOT net> <357C8BB7 DOT 72AB4B6D AT alcyone DOT com> <357ead02 DOT 3535813 AT news DOT Austria DOT EU DOT net> <357ED7CD DOT 6B9D2F0F AT nic DOT smsu DOT edu>
NNTP-Posting-Host: charmaine.alcyone.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Tony O'Bryan wrote:

> There are many other reasons, too, but I just wanted to cover the
> basics.  You
> can, though, use malloc/free and new/delete in the same program as
> long as you
> use them consistently.  People who say to never use malloc in C++
> programs are
> just purists who think malloc should be eliminated.

new/delete is more along the lines of the C++ model, so certainly you
should use them if you are able (they're a lot cleaner and more
straightforward than malloc/free), but they don't allow for resizing,
unless you want to do it yourself.

-- 
         Erik Max Francis, &tSftDotIotE / mailto:max AT alcyone DOT com
                       Alcyone Systems / http://www.alcyone.com/max/
  San Jose, California, United States / icbm:+37.20.07/-121.53.38
                                     \
           She glanced at her watch / . . . It was 9:23.
                                   / James Clavell