T
Tim Kuehn
Guest
Tom - the issue is this isn't a 'short term' decision - Alex stated that whatever they do will be it for the foreseeable future past when 12.0's release. If the decision is error-only, then this becomes useless for larger, long-lived code bases. Cleaning these code bases of these issues would require significant developer effort - or the use of an automated tool that doesn't exist yet (as far as I know). If the decision is warning-only, then each site that wants to mandate strict compile as an absolute requirement will have to write code to catch these warnings and implement their own "error-only" behavior as opposed to simply changing a string setting. An error-only decision means a good idea won't get used where it's needed the most. A warning-only decision means the customer base will need to collectively expend a significant amount of time in order for Progress to save a bit of time on their side.
Continue reading...
Continue reading...