Date:	Thu, 6 Feb 1992 09:41:33 +0100
From:	Ove Ewerlid <ewerlid AT pinus DOT slu DOT se>
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Macros (Was: Re: Reasons not to use DJGPP :-))
References:	<9202052342 DOT AA26944 AT freezer DOT cns DOT udel DOT edu>
Status:	O

> One notable problem, of course, was porting a large quantity of existing
> graphics code intended for Microsoft C. I created a .h file full of macros
								      ^^^^^^
> and whatnot to translate the calls rather than putting a layer of
> expensive function calls in between.

The function inlining support in gcc is *almost* as good as macros.
I ported some gcc developed code to borland C++ 3.0 and noticed
to my horror that bc can't inline functions that contains for loops.
(Fortunately I only use bc as an advanced syntax checking editor :-)

An other problem with bc is that it takes all the available physical memory.
Go into bc and exit via a DOS shell and check how the memory is distributed.
(Using the dos command `mem'.)
I haven't been able to figure out how to tell bc not to clobber all memory.
(There sure are options to do it but they seems to have no effect.
 There is, ofcourse, the risk that I have misunderstood something.)

- Raw text -