PE> NULLZERO.C(6): Error! E1100: Definition of macro 'max' not
 PE> identical to previous definition NULLZERO.C(9): Error! E1011:
 PE> Symbol 'max' has not been declared NULLZERO.C(9): Error! E1054:
 PE> Expression must be constant NULLZERO.C(9): Error! E1020:
 PE> Dimension cannot be 0 or negative Error: Compiler returned a
 PE> bad status compiling 'NULLZERO.C'

 PE> However, that was because the compiler was non-conforming by
 PE> default, and had decided to define a "max" macro on your
 PE> behalf.

  What a good idea!

 PE> It is normal to put your own #defines in uppercase, and call
 PE> them something more descriptive, like MAX_FILES.

  That was the first time I'd used a #define, so I'm not surpised I
got it a bit crossed up. Pascal does it with "const" which is not
nearly as nice as C's macros.

  As for descriptions, I have my own set of obscure names which mean 
things to me. I write code for me, not for anyone else, and the more 
cryptic I can make it, the better.

 PE> I've tried it and it works.  The only change I have made to it is to
 PE> add some comments at the top... 
 PE> /* Written by Bob Lawrence */
 PE> /* Released to the public domain */
 PE> /* Used to clean up archived files in BBS maintenance */

  Whatever you like... it's yours.

Regards,
Bob
 
___ Blue Wave/QWK v2.12
@EOT:

---