Weird behaviour of the syntax checker

Hi *ALL,

i'm using WDSC 5.1.0.1, and i'm starting to use LPEX as editor for
various RPG sources. (Partly because of the excellent teaching and
labs Jon Paris and Susan Gantner gave us at our local common congress
in Vienna, Austria, Europe. Thanks!)

I love the checks for missing/too many () and ', as i tend to
screw them up when i start codin' away.

This works really nice in LPEX showing me e.g. RNF0267E and so on.
That's the way it worked in SEU syntax checking, too. What made me
think of an strategy is that SEU lost this sort of syntax check in
/FREE form. OK, i thought, they really want me to use WDSC.

And now i discover that it is exactly the same!

Take this simple snippet with all appearing messages:

     /FREE
       asking = ''can that be true?';
       thinking = ((as you can't see anything else? pretty dumb...;
      /END-FREE 
     C                   EVAL      OK = ''not with me'
RNF5377E Ende des Ausdrucks erwartet.
     C                   EVAL      OK = function(()
RNF0637E Ein Operand wurde erwartet, aber nicht gefunden; die Bestimmung wird 
ignoriert.
RNF0312E Rechte runde Klammer erwartet, aber nicht gefunden.

So it's clear, fixed form rulez, but i do hope not for very much
longer! May i think i'm right?

Or is there a setting for syntax checks in free form? Then excuse me,
i wasn't able to find it.

Thanks in advance, this whole thing looks very promising, and i'm sure
you and lists like this can work some things out pretty quick, as this
should be the horse IBM is riding at the moment, isn't it? :-)

Thanks in advance!

Anton Gombkötö
senior developer, webmaster
Avenum Technologie GmbH
Vienna, Austria, Europe
http://www.avenum.com

austrian editor of the german-austrian-swiss newspaper "info", webmaster
http://www.common.at

ICT: ag1965