Keith wrote: > Oh, and one other thing ... I despise constructs like: > IF (expr) ELSE do.something > which can *always* be written more clearly as: > IF NOT(expr) THEN do.something
Again, this goes back to the day when machine cycles were precious. Supposedly it saved a couple of cpu instructions, and if it was in the middle of a loop, those cycles could be significant. The MV flavour with which I am currently most familiar is Unidata (and before that Prime/Information, which I haven't touched in 5 years, and before that Microdata Reality, which I haven't touched in 20 years). Do the other compilers support the following construct? IF (expr) THEN do.something ELSE do.something.else I find this tremendously easier to read than: IF (expr) THEN do.something ELSE do.something.else The only problem with using this construct is that it confuses the AE format command ;-) Larry Hiscock Western Computer Services ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
