Yitzchak Scott-Thoennes wrote: >On Thu, Jun 30, 2005 at 02:41:37AM -0700, Yitzchak Scott-Thoennes wrote: > > >>And the table shows that assigning >>a "const char * const []" to a "char * const []" is not valid. >> >> > >Err, I meant assigning a "char * const []" to a "const char * const []" >(i.e. using the cast in MinGW). > Well, using the cast in MinGW is assigning a const char * const * (the caller's argument) to a char * const * (the action of the cast), and then assigning that back to a const char * const * (MinGW's execv's parameter), and both assignments are shown as invalid, so yes, this explains why MinGW (quite correctly) warns when the (unnecessary!) cast is used.
------------------------------------------------ Radan Computational Ltd. The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
