NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/lang/cplus/18202

Text File | 1992-12-21 | 1.9 KB | 42 lines

Newsgroups: comp.lang.c++
Path: sparky!uunet!munnari.oz.au!metro!extro.ucc.su.OZ.AU!maxtal
From: [e-mail] (John MAX Skaller)
Subject: Re: Death of Borland C++ Compiler
Message-ID: <[e-mail]>
Sender: [e-mail]
Nntp-Posting-Host: extro.ucc.su.oz.au
Organization: MAXTAL P/L C/- University Computing Centre, Sydney
References: <[e-mail]>
Date: Fri, 18 Dec 1992 18:43:50 GMT
Lines: 29

In article <[e-mail]> [e-mail] (CHAOLIN CHANG) writes:
>
>I was a loyal Borland C++ compiler user.  I love the IDE environment
>(though I only use it for creating the project file) and various tools
>bundled.  But as my programs are becoming complex (using pointer, pointer
>to pointer, pointer to pointer to pointer and farmalloc extensively),
>Borland compiler begins to fall over.  One of my colleagues is also
>suffering for the same experience when he tried to push the Borland compiler
>to its limits.
>
    PLEASE dont post this kind of thing without saying exactly
what version of the compiler you are using. Also, what compiler
switches? How big is your stack? How much data do you put on
the stack and in the data segment?

    I am using 3.1 and have no such problems. And I have
lots of a->b->c->d[i].f().g() type code :-( [I wont when
I finish packaging it properly] :-)

    Why are you using 'farmalloc'? Do you have any reason not
to use the large model exclusively? Apart from anything else, this
model generally allows portable code to be written while lower
models do not. In the large model, 'malloc' IS 'farmalloc'.

--
;----------------------------------------------------------------------
        JOHN (MAX) SKALLER,         [e-mail]
    Maxtal Pty Ltd, 6 MacKay St ASHFIELD, NSW 2131, AUSTRALIA
;--------------- SCIENTIFIC AND ENGINEERING SOFTWARE ------------------