All the Old Showstoppers

okay, new rule1: it’s okay to install a GObject property like this:

pspec = g_param_spec_string ("title",
			     "The title of the item",
g_object_class_install_property (gobject_class, PROP_TITLE, pspec);

instead of the usual way you see in other GObject-based libraries, where we l33t h4x0rs dispense from the use of an explicit GParamSpec variable. this is especially true if you are trapped in 1983 and are still using an ANSI 80×25 terminal — though you should probably know that here, in 2008, 100+ columns are safe.

oh, and fill out the name and blurb fields of the property: GObject provides a little bit of introspection, but if you willfully ignore it then we can just forget about stuff like the GObject-Introspection project.

please, every time you install a property using a line like this:

g_object_class_install_property (
	gobject_class, PROP_TITLE,
	g_param_spec_string ("title", NULL, NULL, NULL,
	                     G_PARAM_READABLE | G_PARAM_WRITABLE));

an unfortunate incident will involve a bucket of puppies and a belt sander.

comments saying “gobject sucks you should be using ${ZEALOTS_OWN}” will be deleted without mercy because they miss the point by a hundred and fortyseven miles

  1. apologies to Bill Maher []

10 Replies to “All the Old Showstoppers”

  1. yay +1 for that. I’ve been doing in that way where I can anyway because the other way upsets Emacs’ auto-indent

    -1 for saying that 100+ columns are ok though. If I have a wider a screen then I want two side-by-side 80 column windows. And long lines mess up patches in emails

  2. @neil: I respect the fact that some prefer 80 columns — even though I’m not sold on both the window size (use a tiling window manager) or patches in email (fix your email client :-P).

    what I personally find most irritating are the contorsionisms people use to get around the fact that libraries are not using function names like creat() or foo() like it was in 1972. you want to break down the lines? fine. but use a variable or two — or, god forbid, a wrapper inline function. don’t do weird shit like breaking down at parentesis or commas until you cannot distinguish between parameters, functions, macros or ternary operators anymore.

    but I really think it’s time to bite the bullet, if you’re writing C code, and code for non ANSI terminals.

  3. +1 for 80 columns. Because it’s standard, and it’s useful in many situations. Have you heard of printing code, for example? And myself, since I moved from xfwm4 to wmii, I haven’t been able to go back from using a two-column view with a terminal (or two stacked terminals) in the left column and a gvim session in the right column. 80 chars max indeed, I say!

Comments are closed.