🚀 go-pugleaf

grimlok@hubcap.clemson.edu (Mike Percy) writes:

> Sorry.  In large data memory models, malloc() is still not identical to
> farmalloc().  

Guess what the Borland malloc (TC2.0) does in large data models?
"return farmalloc((unsigned long) nbytes)" (believe me, I have the
source). So your large data model programs would be a bit faster, if
you used farmalloc() instead of malloc(). But as you said, they are
not interchangable because the argument of malloc() is an int and the
argument of farmalloc() is long.

> As I said before, it's not really a good idea to explicitly define
> pointers as far/near unless you absolutely must (and know what you're
> doing).  Leaving modifiers off is safe, provided all modules are
> compiled under the same memory model.

Very true - and it is very important to include all the necessary
prototypes, as this example shows us.