home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!usenet.coe.montana.edu!decwrl!csus.edu!borland.com!pete
- From: pete@genghis.borland.com (Pete Becker)
- Newsgroups: comp.lang.c++
- Subject: Re: BC 3.1 TV Running slow ?
- Message-ID: <1992Aug27.190831.4681@genghis.borland.com>
- Date: 27 Aug 92 19:08:31 GMT
- Article-I.D.: genghis.1992Aug27.190831.4681
- References: <1992Aug19.232224.3557@cssc-woll.tansu.com.au> <1992Aug27.073530.9986@info.ucl.ac.be>
- Sender: news@borland.com (News Admin)
- Organization: Borland International
- Lines: 17
- Originator: pete@genghis.borland.com
-
- In article <1992Aug27.073530.9986@info.ucl.ac.be> vijghen@fynu3.fynu.ucl.ac.be (Philippe Vijghen) writes:
- >
- >I had the same problem with a Turbo Vision application and BC++ 3.0
- >compiler. I looked around for a long time and I found that the source
- >of the problem is the memory allocation mechanism: it uses a kind of
- >"safe pool" and a lot of verifications; this certainbly provide advantages
- >but the main result is a important reduction of the speed inside the
- >routines using dynamic memory allocation (I was doing some symbolic
- >computation to implement a fuzzy logic controller).
- >
- >I think that Borland should put an option in his library: speed/security
- >for the mem. alloc., don't you?
- >
-
- Actually, the problem is that the TV library as shipped was built with
- the debugging code left in. If you recompile NEW.CPP with the switch -DNDEBUG
- all the debugging code will go away, and things will be much faster.
-