|
Fuhgeddaboudit. I cannot possibly battle all of you. And you know what? Maybe this mixed mode syntax makes sense, and I just can't see it. Maybe everybody will be coding /free and /end-free in their code from now on, and it will be good. Personally, I think that's ludicrous, and I think five years from now programmers will look at these /codes and say, "Couldn't the compiler writers decide what they wanted to support?". Just think - five years from now someone will pick up a mixed-mode program with embedded SQL and have to know not one, not two, but THREE different syntaxes in order to decipher it. And somehow this is a good thing? I'm very scared. Very scared. Anyway, I'm pretty much the only one saying the emperor has no clothes, so maybe it's just me and I need new glasses. You all think this is a good, smart direction for your shops. I'm tired of this, and I wasted another two hours on it today. No more. I shall drop it, since nobody else seems to give a damn, and everybody is willing to let Hans and company tell them how to write code. Legacy applications be damned - you want new features, rewrite your code! Or use syntax switches! This is the new RPG! Me and Tonto, we're outta here...
This mailing list archive is Copyright 1997-2026 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.