Re: Is this a bug w/ 4GL 4.10

In a recent post, John Maddox wrote. >The following program compiles but does not work as i expect... >Is it me? (or is this a bug?) > Well....let's call it unclear documentation(!?) Stuff deleted... >if x clipped = "" then This is correct syntactically but... I believed this has to do with the way that 'CLIPPED' is implemented and what you're evaluating it against. What exactly does "" mean or represent? It would obviously fail if the x = 'A', but if it was blank filled as you suggest (100x), then what is it comparing. In other words, if clipped is starting at the back slash (\\) and working backwords to find something > ascii 32, how does the result compare with ""? Instead of the above try: IF LENGTH(x CLIPPED) = 0 THEN > display "x is blank" > end if > >end main This brings up a side issue: Who all out there likes to put keywords in all caps and non keywords in lowercase? I find it easier to read and maintain. What about indentation? Since there is no defacto standard, I guess we adopted the approach out of the manuls. I know these are considered 'elements of style' but when you've got a team of people working on this stuff and they get shuffled around from project to project, 'style' can become quite a factor. Don't get me wrong, I relaize that C is lowercase and Unix scripting is mostly as well, however, having everyone on the same sheet of music is often easier for the type of projects and personnel management that I've been exposed to. Just a thought. All flame throwers on 'tepid' please. Jim Sauer Standard Disclaimers Apply