C & C++ string confusion

[bruce.labitt at autoliv.com]

Thanks for the info, Jerry.
-B

gnhlug-discuss-bounces at mail.gnhlug.org wrote on 02/06/2009 02:09:55 PM:

> Just to add a bit more. The C++ versions of the standard C header files 
> should be included:
> For instance:
> #include <cstdio>    NOT #include <stdio.h>
> In all cases of header files defined by the C language standard prepend 
> with a 'c' and drop the '.h'. But, this applies only to the standard C 
> headers. The Unix/Linux standard header, unistd.h and other header files 

> will still use the older syntax. The reason for this is that in some 
> implementations, the C headers may not be C++ clean. Since I do mostly 
> contract programming, I use the "when in Rome" philosophy, but it also 
> applies to coding. When coding in C, code in C, when coding in C++ code 
> in C++.
> 
>>>>> stuff snipped >>>>

******************************
Neither the footer nor anything else in this E-mail is intended to or constitutes an <br>electronic signature and/or legally binding agreement in the absence of an <br>express statement or Autoliv policy and/or procedure to the contrary.<br>This E-mail and any attachments hereto are Autoliv property and may contain legally <br>privileged, confidential and/or proprietary information.<br>The recipient of this E-mail is prohibited from distributing, copying, forwarding or in any way <br>disseminating any material contained within this E-mail without prior written <br>permission from the author. If you receive this E-mail in error, please <br>immediately notify the author and delete this E-mail.  Autoliv disclaims all <br>responsibility and liability for the consequences of any person who fails to <br>abide by the terms herein. <br>
******************************