A
Alex Herbstritt
Guest
A new feature was introduced with 11.7.0 called COMPILER OPTIONS. This feature allows a developer to set rules for the compiler to enforce stricter compilations. The feature is documented under the COMPILE statement [ OPTIONS | OPTIONS-FILE ] phrases : documentation . This new feature grew out of an outreach program with the Progress Communities : Strict mode for the ABL Compiler - Community input is requested There has been continued discussions under Communities through the ESAPs leading up to the release. One particular point discussed was how the compiler reacts when the enabled rules for COMPILER OPTIONS are broken within the compiled source. The initial implementation was to generate an error at the first failure and stop the compilation. This was deemed too difficult to manage by the developer. So, we updated the implementation to generate error messages with each instance of failure but continued the compilation to the end, but do not generate r-code. This is currently how it is implemented in the 11.7.0 FCS. However, there was continued discussion between the final ESAP and the release that not generating r-code makes the feature unusable in certain cases. That brings us to this posting. We are now considering a change for an 11.7 service pack and 12.0 to the feature. We would change the errors generated when the rules for the OPTIONS are broken to warnings and if the only issues seen during the compilation were from the options then we would generate r-code. That is, failing to meet the standards of the COMPILER OPTIONS would result in only warning messages that would not cause the compilation to fail. Again, we would like to hear what the community thinks of this.
Continue reading...
Continue reading...