JK>
  > Only problem is, I don't see how this is going to help you in case of a str
  > that you simply don't know in advance what size it will be.  It's a Catch-2
  > either you must get the string first [gets(string)] and then
  > malloc(sizeof(string)), which isn't really going to help, or you malloc a s
  > for your string first, then gets(string) and hope it fits, which isn't any
  > better than char StrName[some integer].
JK>

  If this is a real concern, use a loop with istream::get(), that
  dynamically allocates a return buffer as it goes along until it reads
  a newline character.  For best results, considering the way that most
  C++ run-time heaps are mannaged, reallocate the return buffer 16 bytes
  bigger every 16 bytes (or use a larger power of two).

  You must remember to destroy the buffer after use, of course.

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 2.02