Since Gil brought it up working with ooRexx at SDI I feel like sharing. While working at SDI the biggest thing I noticed that developers faced with ooRexx was how signals are handle under object oriented code.
When you use directives, signals effectively get reset. Some signals are not always automatically propagated while others are. Combine this problem with the fact that ooRexx is not a typed language and you could have it report an error that was way further down in the code than if the interpreter would have just caught it in the first place. Often I would just adding error trapping to code, so we could figure out what the actual error was. This usually differed greatly with the original error that was displayed to the developer. David Ruggles even wrote a template that consisted of simply adding error trapping to all of the programs that we ran. Having some way of switching the interpreter into a more strict mode (always propagating signals and conditions) would be the most flexible. It can be very confusing to someone who is just trying to get use to the object oriented approach. A lot of times they would just revert to classic code as it was easier to understand. The lesson they often learned was ooRexx encourages classic coding, while slapping you on the wrist if you try to use OO. PS: There is so much code that relies on only using return codes. ooRexx supports return codes and conditions. If everything used conditions and return codes, it could be left up to the developer to use either a classic or object oriented approach to any problem. -- Brandon Cherry ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
