|
> From: Douglas Handy > > With an intelligent converter of fixed to free form, it could > analyze the field > types and lengths and replace all "normal" uses of MOVE with the > proper eval > constructs. This would cover the vast majority of MOVEs. And > make the rest > stick out like the sore thumb they are. Hey, if IBM provided this I'd be thrilled. I'd be mroe thrilled if they also included the %MOVE BIF. Then, we could convert everything, remove all the MOVEs, and still have the %MOVE to "stick out like a sore thumb". See, it really isn't that difficult to come up with a scenario where we're both satisfied. But it does take BOTH sides getting off their butts and meeting in the middle, without this "I'm right and that's all there is too it" attitude. Here's what I'm sick of: I have been REPEATEDLY making suggestions as to things that would improve the language, not crush poor old Hans' vision of the future, and at the same time make legacy programmers' lives easier. And I get stymied every time by some version of the statement, "that old stuff sucks, and it should all be rewritten." What a load of crap! The retesting costs alone would bankrupt most shops! But anyway, you've made your position known. It's diametrically opposed to mine. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.