KK> Just do exactly that! :)
 KK> CONFIG *c;
 KK> int num_of_configs = atoi(argv[1]);
 KK> c = malloc(num_of_configs * sizeof(CONFIG));
 KK> if(!c)
 KK> {
 KK> puts("Malloc error in main() for CONFIG array.");
 KK> return 1;
 KK> }

   Is testing for a 'false pointer', ie, using the logical NOT operator 
   like you did above ANSI standard?  I know that different compilers 
   represent NULL differently, and it's not necessarily (in fact, probably 
   isn't) a pointer with the value zero.  As I understand it, a NULL 
   pointer just points to a predefined invalid address, which is quite 
   likely something outside of the bounds of allowable RAM.
   
   I'm just wondwering whether using this shortcut will compromise code 
   portability- if not, I'll save typing "!=NULL" from now on.  :>
   
... Any given program, when running, is obsolete.
___ Blue Wave/DOS v2.30 [NR]

--- Maximus 2.01wb