A
Alex Herbstritt
Guest
Although the ideas being put forward for extending the feature to allow sub-options that allow either errors and warnings are good, the discussion here is how we handle this in the immediate future. The 11.7 release will be the long term support for OE 11. We are now getting started on 12.0. Since there will be no more major changes for 11.7 in the service packs, we do not have the option of making a major feature upgrade there. Thus, this question is how to address this most simply as possible. For OE 12 we will be focusing on getting new options suggested by Community implemented and may not consider the sub-option concept for quite some time. So, excluding additional changes, what do you see as the preferred way that we handle it. Shall we default to errors and no r-code as it is now, or would you prefer that we generate only warning and produce r-code. Some of the earlier discussions are on the ESAP Community. I don’t know if the ESAP posting are open to the public at large, so those not on the ESAP Community may not have access to them. So go ahead and repeat earlier arguments if you feel strongly enough about them. New compiler options REQUIRE-* messages as warnings instead of errors
Continue reading...
Continue reading...