PF> MD> The compiler will run right through it, never burp at all...  But when
  > MD> you run the program it just acts like it ignores the command.  My
  > MD> question is why doesn't the compiler "Burp" at me? 
This is NOT a
  > MD> command in the Borland run-time library...

PF>Yes, Borland does have this function (it is #defined in mem.h to call memset

Ok.  Why?  I was to the point where I thought it was broken because
setmem would not work (I was thinking memset).  I figured that if it
wasn't the correct command it would burp at me.  So my question is why
is this command supported?

PF>    char myChar[20];
  >    memset(myChar, 0, sizeof(myChar));

So doing the following would not produce the same result?

char *myChar=new char[20];
memset(myChar,0,sizeof(myChar));

Oh, methinks I see!  The size of myChar is 4 because it is a pointer!
Where I was expecting 20... So I should have used sizeof(*myChar)!!!

Michael Douglass
___
 .Mike's Mail Internet:   MICHAEL.DOUGLASS{at}LCHANCE.SAT.TX.US
                   
--- Maximus/2 2.01wb