P
Peter Judge
Guest
Say I have some classes that are using the latest ABL keywords. In particular a new keyword or a keyword that replaces another UDF. Suppose that I want this code to run in multiple versions (let's say 10.2B and later). One approach is to create a branch per supported OE version, and make sure the code is tailored to that OE version. Another approach is to create an include file which can conditionally include stuff based on the PROVERSION or KEYWORD-ALL keywords. There might be other conditional switches (maybe a &GLOBAL-DEFINE of my own that acts as a master switch). In some cases, I will have to branch. For instance, if I am using the JsonObject classes (which are only in 11.0+), the code in 10.2B cannot be easily conditionally included/excluded. However, there are cases where I can write an include which can use either the new ABL GET-FOO() statement or my fnGetFoo() UDF. I see the conditional approach as being useful because it means I only have to maintain a single branch of this code. It can get mighty unreadable and potentially unwieldy. Thoughts? -- peter -- peter
Continue reading...
Continue reading...