Re: va_list and char* are ambiguous

2014-03-03 Thread Irfan Adilovic
On Mon, Mar 3, 2014 at 1:47 PM, Kai Tietz wrote: > Hi, > > cygwin64 shares for 64-bit the ABI of Windows native. This is caused > by different reasons (eg. unwind-table description for prologue, etc). > So for Windows targets va_list is indeed of 'char *' type. And this > is ok. The variant of x

Re: va_list and char* are ambiguous

2014-03-03 Thread Kai Tietz
Hi, cygwin64 shares for 64-bit the ABI of Windows native. This is caused by different reasons (eg. unwind-table description for prologue, etc). So for Windows targets va_list is indeed of 'char *' type. And this is ok. The variant of x86_64 abi, which uses indeed a structure-variant for variadi

Re: va_list and char* are ambiguous

2014-03-02 Thread Irfan Adilovic
On Sun, Mar 2, 2014 at 10:50 PM, Václav Zeman wrote: > On 03/02/2014 10:45 PM, Irfan Adilovic wrote: >> On Sun, Mar 2, 2014 at 6:58 PM, Irfan Adilovic wrote: >>> irfan@irfy:~$ cat x.cc >>> #include >>> #include >>> using namespace std; >>> void foo (...){ cout << "varargs\n"; } >>> void f

Re: va_list and char* are ambiguous

2014-03-02 Thread Václav Zeman
On 03/02/2014 10:45 PM, Irfan Adilovic wrote: > On Sun, Mar 2, 2014 at 6:58 PM, Irfan Adilovic wrote: >> irfan@irfy:~$ cat x.cc >> #include >> #include >> using namespace std; >> void foo (...){ cout << "varargs\n"; } >> void foo (va_list ap) { cout << "va_list\n"; } >> int main () { >>

Re: va_list and char* are ambiguous

2014-03-02 Thread Irfan Adilovic
On Sun, Mar 2, 2014 at 6:58 PM, Irfan Adilovic wrote: > irfan@irfy:~$ cat x.cc > #include > #include > using namespace std; > void foo (...){ cout << "varargs\n"; } > void foo (va_list ap) { cout << "va_list\n"; } > int main () { > foo ((const char *)NULL); > foo ((char *)NULL); >