Consider this declaration: Cancellable c;
and somewhere else, before c is initialized, there is this call: c.cancel (); Guess what will happen? Expectation: 1- best: compiler detects this. 2- acceptable: crashes. 3- acceptable: runtime error messages (like in gtk). What actually happens: The program continues running, hiding the bug, puzzling the programmer as the application slows down due to async processes consuming the cpu. The fault is partly due to glib. Perhaps "g_cancellable_cancel(null)" makes sense, but "null.cancel()" simply doesn't. Any chance of vala compiler (or vapi) helping here by asserting non-null before passing to glib functions? hand Nor Jaidi Tuah _______________________________________________ vala-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/vala-list
