|
On 03/18/2016 10:33 AM, Nicolas George
wrote:
[ Replying a little randomly to this message. ] Randall Sawyer: Three answers: 1) Interface Developer Support 2) Relevant reusable code 3) Completeness bash-4.3$ pwd /usr/src/gtk+-3.18.5_1/gtk bash-4.3$ grep -l g_utf8_offset_to_pointer *.c gtkentry.c gtkentrybuffer.c gtklabel.c gtkpango.c gtktextbtree.c gtktextbuffer.c gtktextiter.c gtktextlayout.c bash-4.3$ grep -l g_utf8_pointer_to_offset *.c gtkentry.c gtkfilechooserentry.c gtklabel.c gtkpango.c gtkprintoperation.c Looking through the function definitions in the source files listed above, I see the same procedures being performed repeatedly and the same sorts of parallel storage of byte length and code point ("character" - in Gtk parlance) length in string storage structures. Wouldn't it make for cleaner code and for more flexible extensibility for developers if the glib API were to provide these in the background to begin with? Thanks to all. PS: /usr/src is where I put untarred distributed source for some of the packages I have installed. _______________________________________________ gtk-devel-list mailing list gtk-devel-list gnome org https://mail.gnome.org/mailman/listinfo/gtk-devel-list |