From: Emmanuel S. [ES] <ma...@ei...> - 2007-07-18 16:45:57
|
I have some code that compiles for VC++ which uses the Microsoft specific extension i64 and ui64 to write an 64-bit integer constant in my source code. Now this is not understood out of the box by gcc. Is there a solution that does not involve changing all my source code? Thanks, Manu ------------------------------------------------------------------------ Eiffel Software 805-685-1006 http://www.eiffel.com Customer support: http://support.eiffel.com Product information: mailto:in...@ei... User group: http://groups.eiffel.com/join ------------------------------------------------------------------------ |
From: Erik de C. L. <mle...@me...> - 2007-07-18 20:47:01
|
Emmanuel Stapf [ES] wrote: > I have some code that compiles for VC++ which uses the Microsoft specific > extension i64 and ui64 to write an 64-bit integer constant in my source > code. Now this is not understood out of the box by gcc. The "i64" and "ui64" extensions are non-standard microsoft specific extensions. The ISO C Standard uses "ll" and "ull" instead. > Is there a solution that does not involve changing all my source code? You will still need to make some changes, but I use something like this ins single header file: #ifdef _MSC_VER typedef __int64 int64_t ; #define PLATFORM_S64(x) x##i64 #else #include <stdint.h> #define PLATFORM_S64(x) x##ll #endif and then use int64_t whatever = PLATFORM_S64 (0xbadc0debadc0de) ; HTH, Erik -- ----------------------------------------------------------------- Erik de Castro Lopo ----------------------------------------------------------------- With 22,100,000 legitimate businesses in the US alone, allowing each to send only one UCE per *year* gets every mailbox 60,547 emails per day. There will either be email without UCE or there will be no email. |
From: Ramiro R. P. <ra...@li...> - 2007-07-18 23:01:01
|
Erik de Castro Lopo wrote: > Emmanuel Stapf [ES] wrote: > > >> I have some code that compiles for VC++ which uses the Microsoft specific >> extension i64 and ui64 to write an 64-bit integer constant in my source >> code. Now this is not understood out of the box by gcc. >> > > The "i64" and "ui64" extensions are non-standard microsoft specific > extensions. The ISO C Standard uses "ll" and "ull" instead. > > >> Is there a solution that does not involve changing all my source code? >> > > I suggest you change all your source code to use portable PRI* C99 macros, and use msinttypes for MSVC++ from: http://code.google.com/p/msinttypes/downloads/list It's much better to write portable code. Ramiro Polla |
From: Emmanuel S. [ES] <ma...@ei...> - 2007-07-19 04:37:13
|
Thanks. I've used something similar to what you are proposing and it works just great. Regards, Manu > -----Original Message----- > From: min...@li... > [mailto:min...@li...] On Behalf > Of Erik de Castro Lopo > Sent: Wednesday, July 18, 2007 1:47 PM > To: min...@li... > Subject: Re: [Mingw-users] i64 and ui64 suffix not recognized > > Emmanuel Stapf [ES] wrote: > > > I have some code that compiles for VC++ which uses the Microsoft > > specific extension i64 and ui64 to write an 64-bit integer > constant in > > my source code. Now this is not understood out of the box by gcc. > > The "i64" and "ui64" extensions are non-standard microsoft > specific extensions. The ISO C Standard uses "ll" and "ull" instead. > > > Is there a solution that does not involve changing all my > source code? > > You will still need to make some changes, but I use something > like this ins single header file: > > #ifdef _MSC_VER > typedef __int64 int64_t ; > #define PLATFORM_S64(x) x##i64 > #else > #include <stdint.h> > #define PLATFORM_S64(x) x##ll > #endif > > and then use > > int64_t whatever = PLATFORM_S64 (0xbadc0debadc0de) ; > > HTH, > Erik > -- > ----------------------------------------------------------------- > Erik de Castro Lopo > ----------------------------------------------------------------- > With 22,100,000 legitimate businesses in the US alone, > allowing each to send only one UCE per *year* gets every > mailbox 60,547 emails per day. There will either be email > without UCE or there will be no email. > > -------------------------------------------------------------- > ----------- > This SF.net email is sponsored by DB2 Express Download DB2 > Express C - the FREE version of DB2 express and take control > of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > |
From: David L. <yak...@ya...> - 2007-07-19 18:37:21
|
Is there anywhere a version of MSYS whose console works well in Vista 64. The MSYS console entered in a self executing loop until it reaches a big number of consoles, then windows closes all of them, but I cannot enter the console. I read someone had found a workaround or something, but I don't know where to find it. Thanks in advance. ____________________________________________________________________________________ Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html |
From: Tuomo L. <dj...@ik...> - 2007-07-19 18:51:21
|
David Lucena wrote: > Is there anywhere a version of MSYS whose console works well in Vista 64. The MSYS console entered > in a self executing loop until it reaches a big number of consoles, then windows closes all of > them, but I cannot enter the console. > > I read someone had found a workaround or something, but I don't know where to find it. Well, I can't help you, though the problem sounds familiar. How about searching the archives? For this list and the Mingw-Msys list. Incidentally, what does this have to do with "Re: [Mingw-users] i64 and ui64 suffix not recognized"? That is the subject of the message you responded to (message id <669...@we...>). -- Tuomo ... Brooke's Law: Whenever a system becomes completely defined, some damn fool discovers something which either abolishes the system or expands it beyond recognition |
From: David L. <yak...@ya...> - 2007-07-19 19:22:08
|
--- Tuomo Latto <dj...@ik...> escribió: > David Lucena wrote: > > Is there anywhere a version of MSYS whose console works well in Vista 64. The MSYS console > entered > > in a self executing loop until it reaches a big number of consoles, then windows closes all of > > them, but I cannot enter the console. > > > > I read someone had found a workaround or something, but I don't know where to find it. > > Well, I can't help you, though the problem sounds familiar. > How about searching the archives? > For this list and the Mingw-Msys list. > > > Incidentally, what does this have to do with > "Re: [Mingw-users] i64 and ui64 suffix not recognized"? > That is the subject of the message you responded to > (message id <669...@we...>). I just reply the last received message from the mailing list and changed the subject and contents. I do this always in other mailing lists and works. Maybe this is a little different and keeps track of other data although I cannot understand how. I think that the recipient was not changed, so the list must have kept track of the latest recipient post or something. Sorry for that. ____________________________________________________________________________________ Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html |
From: Keith M. <kei...@us...> - 2007-07-19 20:58:16
|
On Thursday 19 July 2007 20:21, David Lucena wrote: > I just reply the last received message from the mailing list and > changed the subject and contents. I do this always in other mailing > lists and works. In your own interest, you should NEVER, EVER do this! > Maybe this is a little different and keeps track of > other data although I cannot understand how. I think that the > recipient was not changed, so the list must have kept track of the > latest recipient post or something. No, there is nothing different. I explained this two or three times before; maybe one day, the message will sink in. EVERY message you send is assigned an ID. When you reply to a message, your reply also contains a reference, by ID, to the message to which you reply; threading mail clients, and web archives use the chain of backward references, to collect messages into threads. When you hijack an existing thread, your message is hidden in the depths of the thread you hijacked. This happens, on EVERY list in which you engage in this anti-social behaviour. It's mildly annoying, when following a thread, to find an unrelated message encroaching, but it's not to difficult to simply skip, and ignore the diversion; the real problem, which you should worry about, is that, because you've chosen to hide your enquiry in an unrelated thread, it's less visible to the very people you are hoping might answer it, and they are much more likely to ignore you. To give yourself the best possible chance of getting an effective answer, you should ALWAYS start a completely new thread for each new topic. Regards, Keith. |
From: Cesar S. <ces...@gm...> - 2007-07-20 22:49:31
|
David Lucena wrote: > Is there anywhere a version of MSYS whose console works well in Vista 64. There isn't such a version yet, but there is work being done on it. > I read someone had found a workaround or something, but I don't know where to find it. The workaround is within the source code for the msys-1.0.dll file. At the moment, you need to patch the source code and build your own version. When the remaining issues are solved, a compiled version should become available for testing. If you are interested, the latest patch and the development discussion can be found here: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1674783&group_id=2435 Regards, Cesar |