On Sun, Jan 2, 2011 at 9:13 PM, Andrew Whitworth <[email protected]> wrote: > On Sun, Jan 2, 2011 at 5:25 PM, Peter Lobsinger <[email protected]> wrote: >> The hit assertion is for sig_str, which is legitimate. Every NCI >> function *must* have a signature in order to be able to determine how >> to map PCC to the native ABI. sig_str being null is *not* a valid >> state for this object, and the assertion is appropriate. > > I would disagree, to a point. Obviously sig_str in invoke is an error > condition but the correct behavior is to throw an exception, not fail > an assertion.
There are a lot of places in parrot where abnormal and unintended uses catch on assertions. Should all of these be exceptions? Do we have guidelines on what should be exception-guarded and what should be assertion-guarded? Is the distinction between assertion and exception useful in parrot? My preference lies squarely with assertions because they are dead simple to track down with a debugger, but I am bit of a gdb junky. > --Andrew Whitworth > _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
