M
Mike Fechner
Guest
Problem is, that just for something as pointless as an additional white space to a single line comment, I would not introduce potential adoption blockers for new versions of Progress. Reality is, that development managers would more likely vote to stick on an old release than upgrading to the latest version of OpenEdge when code changes – especially just for something as valueless a new comment syntax – are required. And in all our interest we want the whole community to move to most recent releases ASAP. I think it would be a huge mistake to break backwards compatibility for a new comment syntax. //{space|tab}comment Is the way to go. Or a completely different character. But then the point of making it easy for JavaScript-kiddies using Rollbase/Kendo UI/Modulus to understand ABL a little bit better is blown away. I am sure they can understand an extra space. Von: Simon L. Prinsloo [mailto:bounce-simonvidisolvecom@community.progress.com] Gesendet: Freitag, 22. Mai 2015 08:27 An: TU.OE.Development@community.progress.com Betreff: RE: [Technical Users - OE Development] Single Line Comments RE: Single Line Comments Reply by Simon L. Prinsloo I have not and if my code base has that anywhere I would be willing to fix it, rather than to accept some awkward alternative. Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...