Re: Conflict between windows.h and giomm/dbusmessage.h (2)
- From: John Emmas <johne53 tiscali co uk>
- To: gtkmm <gtkmm-list gnome org>
- Subject: Re: Conflict between windows.h and giomm/dbusmessage.h (2)
- Date: Mon, 19 Aug 2013 16:38:42 +0100
On 19/08/2013 16:08, Jonas Platte wrote:
I already answered to your previous mail, I don't know why you didn't
receive my reply.
But you can read it on the mail archive:
https://mail.gnome.org/archives/gtkmm-list/2013-August/msg00115.html
My apologies Jonas. Your first reply went to my 'Deleted Items' folder
for some strange reason (probably finger trouble on my part. I've never
known it to happen before). Anyway, to answer your questions....
On 16/08/2013 09:05, Jonas Platte wrote:
If you have no special reason to use winsocks, you should better just
use the socket class which comes with Giomm, Gio::Socket.
I'm not actually using sockets. I just gave that as an example of a
situation where windows.h might get #included without the user being
aware of it.
On 16/08/2013 09:05, Jonas Platte wrote:
Have you tried only including giomm.h and windows.h
Yes - from my original example:-
#include <windows.h>
#include <giomm.h> // ( or alternatively, #include
<giomm/dbusmessage.h> )
Creating a source file with just those 2 lines gives me the
following compiler error:-
dbusmessage.h(353) : error C2332 'struct' : missing tag name
Hope that clarifies things. I realise of course that I could simply
swap the order of the #included files but that's not an acceptable
solution IMHO. Whenever a program's behaviour (or ability to compile)
is dependent on the order of #included files, that's invariably a bad
sign in my experience.
John
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]