>A friend of mine who is a Clarion programmer send me some code the other day. He said it was just one small example of the monstosity of a language that is it:
>
>...
>GOSUB 9000
>GOSUB 5000
>IF DCHG < .01 GOTO 4560
>GOTO 4200
>4170 GOSUB 50000
>GOTO 4150
>4180 GOSUB 8550
>GOTO 4150
>..
>
>And another:
>
>INPUT @RV,@(19,15)DECDT$[1,2],_
>@(19,18)DECDT$[3,2],_
>@(19,21)DECDT$[5,2]|
>CTL=3400,3350,1000,99999,_
>3420,3430,4590,8650
>
>That's just one long command...
>
>Ok, altogether now: "Thank you foxpro, thank you foxpro, thank you foxpro"...

Had a boyfriend who was a Clarion programmer and he kept wanting me to move to Clarion because "it's SO much better and faster than Fox ". Kept telling him I wasn't interested and he swore he would prove it to me. Well, the opportunity came up for just that. Friend needed a program that would read an .SDF off a floppy, dump the info into a .DBF and wanted a screen to view/edit the data. Took me 8 hours (total) and it would 1) make sure that there WAS a floppy in the drive (either drive), append into the .DBF and his screen would allow single item lookup, a browse function, and of course, the editing functions. When I was finished, Morgan sat down and started working on the same thing in Clarion. 15 hours later, he was ready to do primary testing/debugging. 10 hours after that (after I had already delivered the Fox and gotten the money) he was almost finished except that it took about 3X as long to create the .dbf. He eventually got it working in a reasonable amount of time by calling my FOX .dbf creation module and THEN porting into Clarion. Needless to say, he heard QUITE a bit from me about this little test ("Oh yeah....tell me AGAIN how Clarion is so much better?), and needless to say we didn't date for much longer after that.....<grin>.