M
Mike Fechner
Guest
This is what I use to test for 10.2A and above: &IF NOT PROVERSION GE "4" AND PROVERSION GE "10.2A" &THEN &GLOBAL-DEFINE winkitactive &ENDIF Not nice – but works. Von: jmls [mailto:bounce-jmls@community.progress.com] Gesendet: Mittwoch, 7. Mai 2014 21:20 An: TU.OE.Development@community.progress.com Betreff: is Keyword now irrelevant ? is Keyword now irrelevant ? Thread created by jmls for some time I used to use the keyword() function in preprocessor &IF statements to check if certain features were present while compiling. However, I tried to use this today for checking for Json Object support. Much to my initial surprise, all the json support "keywords" came back as ? , even under 11 Thinking about it, I realised that these aren't keywords. They are new progress classes (much like AppError) and don;t show on the keyword() hit list Does this mean that keyword is actually becoming useless and should be marked as deprecated ? If more and more language features are being implemented as classes then the keyword function becomes less and less relative I know that I could use the proversion function in the preprocessor, but I didn't want to have to remember which version of progress a particular feature was implemented while I'm at it, is there a quick way of checking at compile time using preprocessors if the running version is 10.2B ? Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...