2011/3/3 Rick McGuire <object.r...@gmail.com> > A second guess here. If SIGNAL ON ANY is used, then this is probably > trapping the NOMETHOD condition. If nothing is trapping the NOMETHOD > condition, then the SYNTAX error is raised. There are no error codes > or message associated with NOMETHOD. > > ah, yes, you're rigtht... Because of copy-paste, I had twice 'signal on syntax' in my test case. Now, I get the same infos for 'signal on nomethod' and 'signal on any' (.nil).
The 'signal on syntax' brings more informations. So now my question is : for ANY and NOMETHOD (and others probably), why don't we bring the same informations as 'signal on syntax' ? I understand from the doc that some entries in the condition directory are only for SYNTAX. Just curious to know why this limitation to SYNTAX. I attached my test case. Inside, there is the output for each case : ANY, SYNTAX, NOMETHOD. My initial problem : I wanted a kind of 'catch all' which cleans some resources in case of error. And I displayed condition~message to have an idea of the error. But i got only .nil. Regards Jean-Louis
condition.rex
Description: Binary data
------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
