FidoNet Echomail Archive
aust_c_here

<<< Previous Index Next >>>

From: Frank Adam
To: All
Date: 1997-01-17 05:37:00
Subject: To cast or not to cast ?

Hi guys,

While looking at clues to why my program was chewing up memory, this 
hit my eyes..

From the borland technical manuals <ti738.asc>.
 "
  Failure to include ALLOC.H is a common mistake. When ALLOC.H is
  left out the type checking is not performed. Since there is no
  prototype the memory allocation functions are all thought by the
  compiler to be returning integer types. A program will usually
  continue to work without ALLOC.H in the near memory models, since
  an integer is the same size as the near pointers used in these
  memory models. However in the far memory models the segment half
  of the pointer is lost when the memory allocation function
  attempts to return a far pointer. These programs may or may not
  work. You should always include ALLOC.H.
 "
  
Forget the last line, but..Does this say what i think it does ? 
Just when i got used to not casting in C ?..

  L8r Frank(fadam{at}ozemail.com.au)

___ Blue Wave/DOS v2.21

---
 * Origin: Melbourne PC User Group BBS (3:632/309)
SEEN-BY: 633/267 270
@PATH: 632/309 107 360 50/99 635/728 633/267



<<< Previous Index Next >>>