[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MinGW port
From: |
Nils Durner |
Subject: |
Re: MinGW port |
Date: |
Sat, 09 Sep 2006 20:14:18 +0200 |
User-agent: |
Thunderbird 1.5.0.5 (Windows/20060719) |
Hi,
first of all, sorry for the late reply.
>> - execv (exec_file, exec_argv);
>> + execv (exec_file,
>> +#ifdef __MINGW32__
>> + (const char * const *)
>> +#endif
>> + exec_argv);
>
> Thanks for the patch, but do you understand exactly what the
> Win32/MinGW compiler is complaining about?
No, I don't.
IMHO, gcc treats "const char *const *" wrong.
> I thought it was generally
> OK to pass a non-const value to a function whose corresponding
> parameter is declared as const.
Right.
The sample code for execv() at
http://msdn.microsoft.com/library/en-us/vccore98/HTML/_crt__execv.2c_._wexecv.asp
triggers the same warning with GCC.
I have no access to a Visual C compiler ATM, but I doubt MS' sample code
causes warnings with their compiler.
Regards,
Nils