https://bugzilla.novell.com/show_bug.cgi?id=318894
User [EMAIL PROTECTED] added comment https://bugzilla.novell.com/show_bug.cgi?id=318894#c7 --- Comment #7 from Paolo Molaro <[EMAIL PROTECTED]> 2008-10-10 07:41:35 MDT --- Coding guidelines: a space is needed after function names, if, etc. ints need to be cast to gpointer using GINT_TO_POINTER, no space after !, gmalloc doesn't return NULL, no explicit type when casting from void*, add a space between ) and {. This behaviour can be enabled by calling a function in the runtime that sets a flag. Jim, chaining would be the right thing to do, if it was easy and possible to do it correctly. If it's not completely transparent, apps need to be aware and they tell us they are aware using the suggested function call. Examples of signals where in_managed would be wrong include INT, the signal to enable/disable tracing, SEGV, the signal to get a thread dump. As for the test, we don't have a particularly good setup for those tests. It should be coded in perl as that is already a dependence for running tests and we don't really want other dependencies imposed on users. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
