I just tried rebuilding my GTK apps for a 64 bit Linux system (Fedora core 5), and had an ugly surprise: random segmentation faults. I traced at least one of them to my lazy habit of using a literal zero in place of NULL for an optional function argument or end-of-arg-list indicator. I speculate that the compiler is supplying a 32 bit zero where a 64 bit zero is needed. Correct? If so, it seems this is a compiler bug, since the type conversion should be automatic. Can someone confirm this?
-- View this message in context: http://www.nabble.com/using-literal-zero-for-NULL-t1316047.html#a3508418 Sent from the Gtk+ - Dev - General forum at Nabble.com. _______________________________________________ gtk-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtk-devel-list
