Re: [Mingw-w64-public] PRIu64 and uint64_t

2013-06-11 Thread JonY
On 6/11/2013 15:55, Koehne Kai wrote: > > >> -Original Message- >> From: Jim Michaels [mailto:jmich...@yahoo.com] >> Sent: Tuesday, June 11, 2013 9:23 AM >> To: mingw-w64-public@lists.sourceforge.net >> Subject: Re: [Mingw-w64-public] PRIu64 and uint6

Re: [Mingw-w64-public] PRIu64 and uint64_t

2013-06-11 Thread Koehne Kai
> -Original Message- > From: Jim Michaels [mailto:jmich...@yahoo.com] > Sent: Tuesday, June 11, 2013 9:23 AM > To: mingw-w64-public@lists.sourceforge.net > Subject: Re: [Mingw-w64-public] PRIu64 and uint64_t > > > why would I want to use __mingw_printf?

Re: [Mingw-w64-public] PRIu64 and uint64_t

2013-06-11 Thread Jim Michaels
c library or c++ library stuff. this is news to me, and I have been working with mingw-w64 for a few years now - lost count. new feature? > > From: JonY >To: mingw-w64-public@lists.sourceforge.net >Sent: Monday, June 10, 2013 3:06 AM >Subject: Re:

Re: [Mingw-w64-public] PRIu64 and uint64_t

2013-06-10 Thread JonY
On 6/10/2013 18:06, JonY wrote: > On 6/10/2013 14:07, Jim Michaels wrote: >> is there a way to detect compilation with --ansi or --posix? >> > > No, this should not be needed, the correct inttypes macro will be used > corresponding to the printf set. C99 printf with __mingw_printf etc... > Ther

Re: [Mingw-w64-public] PRIu64 and uint64_t

2013-06-10 Thread JonY
On 6/10/2013 14:07, Jim Michaels wrote: > is there a way to detect compilation with --ansi or --posix? > No, this should not be needed, the correct inttypes macro will be used corresponding to the printf set. C99 printf with __mingw_printf etc... I have not investigated this further. signa

Re: [Mingw-w64-public] PRIu64 and uint64_t

2013-06-09 Thread Jim Michaels
is there a way to detect compilation  with --ansi or --posix? > > From: Tony Theodore >To: Gunnar >Cc: mingw-w64-public@lists.sourceforge.net >Sent: Sunday, June 9, 2013 8:26 PM >Subject: Re: [Mingw-w64-public] PRIu64 and uint64_t > &

Re: [Mingw-w64-public] PRIu64 and uint64_t

2013-06-09 Thread Tony Theodore
On 03/06/2013, at 2:52 AM, Gunnar wrote: > In MinGW564 the code: > > #define __STDC_FORMAT_MACROS 1 > #include > > .. > .. > > uint64_t i = 0; > printf("i = %" PRIu64 "\n", i); > > > > leads to a "unknown conversion type character 'l' in format". In MiGW32 it > compiles witout a warning.

[Mingw-w64-public] PRIu64 and uint64_t

2013-06-09 Thread Gunnar
In MinGW564 the code: #define __STDC_FORMAT_MACROS 1 #include .. .. uint64_t i = 0; printf("i = %" PRIu64 "\n", i); leads to a "unknown conversion type character 'l' in format". In MiGW32 it compiles witout a warning. The command that I use is x86_64-w64-mingw32-gcc-4.8.0.exe -fexception

Re: [Mingw-w64-public] PRIu64 and uint64_t

2013-06-03 Thread JonY
On 6/3/2013 20:16, Rafaël Carré wrote: > Le 03/06/2013 13:00, Gunnar a écrit : >> In MinGW564 the code: >> >> #define __STDC_FORMAT_MACROS 1 >> #include >> >> .. >> .. >> >> uint64_t i = 0; >> printf("i = %" PRIu64 "\n", i); >> >> >> >> leads to a "unknown conversion type character 'l' in format".

Re: [Mingw-w64-public] PRIu64 and uint64_t

2013-06-03 Thread Rafaël Carré
Le 03/06/2013 13:00, Gunnar a écrit : > In MinGW564 the code: > > #define __STDC_FORMAT_MACROS 1 > #include > > .. > .. > > uint64_t i = 0; > printf("i = %" PRIu64 "\n", i); > > > > leads to a "unknown conversion type character 'l' in format". In MiGW32 it > compiles witout a warning. > >

[Mingw-w64-public] PRIu64 and uint64_t

2013-06-03 Thread Gunnar
In MinGW564 the code: #define __STDC_FORMAT_MACROS 1 #include .. .. uint64_t i = 0; printf("i = %" PRIu64 "\n", i); leads to a "unknown conversion type character 'l' in format". In MiGW32 it compiles witout a warning. The command that I use is x86_64-w64-mingw32-gcc-4.8.0.exe -fexception