Re: Why keysym constants in gdk/gdkkeysyms.h are defined as macros, not as an enum?

-sized integer to store an enum, so > sizeof of an enum type can change if you add more values to it, which > could be an ABI break. And this is not purely theoretical, I think > llvm does this. > This is only a problem if you use the enum data type. -- André Gillibert ___

Re: Reducing unncessary string copying

2012/2/20, Enrico Weigelt : > * André Gillibert schrieb: > >> This adds some level of indirection to access the data bytes, and some >> space overhead. >> For example, the string "hello" is 6 bytes long (including the zero >> terminator), with GLIBC'

Re: Reducing unncessary string copying

nce overhead would incur. Moreover, I can think of a better implementation (still not worth it, in my opinion). Storing the string as an array of bytes. The first byte of the array would be the "static" bit, and the rest would be the string data. The actual GStr* object would be a pointe

GIO performance improvements

1.2, but I may wrote similar patches for Nautilus. -- André Gillibert ___ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list