> We have to agree on which error raising macro is used where. It doesn't make > sense to go back and forth between "throw XQUERY_EXCEPTION" and "RAISE_ERROR".
RAISE_ERROR was something that Markos introduced. It's completely unnecessary. It gratuitously changes the order or the arguments. It doesn't work for ZORBA_EXCEPTION (which often means that code is incorrectly throwing an XQueryException rather than a ZorbaException where a ZorbaException is the correct exception to throw). There are 4 flavors of the macro that are difficult to remember. Those 4 flavors don't even cover all cases. These macros are similar to the original, ugly error macros. Since Markos is intransigent, the only thing we can do is to not approve merge proposals if anybody other than Markos uses the macros. -- https://code.launchpad.net/~paul-lucas/zorba/bug-1147518/+merge/158449 Your team Zorba Coders is subscribed to branch lp:zorba. -- Mailing list: https://launchpad.net/~zorba-coders Post to : zorba-coders@lists.launchpad.net Unsubscribe : https://launchpad.net/~zorba-coders More help : https://help.launchpad.net/ListHelp
