M
Mike Fechner
Guest
An API is a tool provided to other developers as a black box. Like the Http client. I tend to program in a way that errors are thrown or handled. But not left behind unhandled. NO-ERROR is a bad thing. I have even requested a SonarCobe rule against it. FIND is an exception. I prefer to do the CAN-FIND/FIND thingie or the IF AVAILABLE ... ELSE ERROR-STATUS:ERROR NO-ERROR. When it's really a huge problem, when the record is not there I don't use NO-ERROR at all and use a CATCH block. Sent from Nine Von: Peter Judge Gesendet: Montag, 5. Februar 2018 17:58 An: TU.OE.Development@community.progress.com Betreff: RE: [Technical Users - OE Development] May OpenEdge classes set the error-status? Update from Progress Community Peter Judge Do you – as a general rule – clear the ERROR-STATUS:ERROR flag ? And what do you consider an API? View online You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here . Flag this post as spam/abuse.
Continue reading...
Continue reading...