-=> Quoting Darin Mcbride to Tika Carr <=-
 DM> of it, is your answer.  Kinda a poor paraphrase, I know, but I'm just
 DM> saying that when your solution is to use a static, use it.  Sometimes
 DM> it is cleaner to use a static than to not.
That's true, however, it still will "bug" me. I get too* picky sometimes.
Comes from the "old days" of computing where every byte counts. I still can't
get over the fact we can have MB's of Hard drive space and RAM. :)
 DM> char* SomeProgramDirectory()

 DM> No matter how many times I use the directory path, I only search for
 DM> it once. It gives me a simple "cache" for this value.
That's a neat idea. I'll snag that snippet. The idea may come in handy in a
few things - thanks!
 DM> If there is space available, realloc *CAN* (but doesn't have to) use
 DM> it to grow.  When it shrinks, it can *NOT* move other memory around to
 DM> use up the extra space created.
I now see why realloc isn't a very good idea. Another frivolous library
function??
Tika
The 3:00 am Club: http://www.geocities.com/SiliconValley/Haven/1420/
Tika Carr: tika@knightmoves.com [C/C++ Code, Libraries, Info...]
... Windows: Ultimate memory manager.  It manages to use it all.
___ Blue Wave/DOS v2.30
--- QScan/PCB v1.17b / 01-0406
---------------