Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

Performance When Converting Legacy Dates

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Performance When Converting Legacy Dates

    ** This thread discusses the article: Performance When Converting Legacy Dates **
    ** This thread discusses the Content article: Performance When Converting Legacy Dates0

  • #2
    Re:Performance When Converting Legacy Dates

    ** This thread discusses the article: Performance When Converting Legacy Dates **
    Hi Sam, I agree with your conclusions and would also add a fourth reason for choosing the MONITOR approach - not juts with dates but with similar situations like potential record locks, divide by zero, decimal data error, etc. Using MONITOR makes it obvious what the programmer _expected_ to happen. When reading a program and encountering a MONITOR op-code you are immediately reminded that a problem may arise in the code that follows. You then get to see what logic sequence the programmer regards as the "normal" process. You then get to see exactly what possible errors the programmer anticipated and the recovery logic associated with each case. Using TEST, or and IF x <> 0, or ... doesn't give you that kind of information. You have to read and understand all of the logic before you know what is really going on.

    Comment

    Working...
    X