Thu Aug 11 04:46:12 PDT 2011
- Previous message: [Slony1-bugs] [Bug 230] Timestamps stopped showing up in the slon_log on some platforms
- Next message: [Slony1-bugs] [Bug 230] Timestamps stopped showing up in the slon_log on some platforms
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=230 --- Comment #4 from Steve Singer <ssinger at ca.afilias.info> 2011-08-11 04:46:12 PDT --- (In reply to comment #3) > The definition seems generally reasonable. > > One caveat is that ~ isn't portable when applied to signed operands, so if we > have any platforms where bool has, underlying it, a signed type, then there > could be some unhappiness. I suspect this is the root cause of the unhappiness to begin with, I think this patch makes the casting happen on both sides of the operator. Should we just do #define true (bool) 1 #define false (bool) 0 ? -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
- Previous message: [Slony1-bugs] [Bug 230] Timestamps stopped showing up in the slon_log on some platforms
- Next message: [Slony1-bugs] [Bug 230] Timestamps stopped showing up in the slon_log on some platforms
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list