>your my girl!

"You're my girl"... as in "You are my girl."

>I even never ever use i but always describe it like e.g.
>
>For liPersonCNt = 1 to ThisForm.loPerson,Count()
>blah blah
>EndFor
>
>hate reading codings with all those i, j, a.s.o. afterall we have ISX installed isn't it?

Using single-letter loop variables isn't too bad if it's like this:
for i = 1 to 5
someFunction(i)
next
because everywhere you look it's fully in context. Anything beyond that tight little loop, and it's a bad idea. And I actually would never do that either, but would use lnI instead as well.

>And for me M.txt would be a showstopper.

I've seen apps which take properly written source code and obfuscate it to the point where all variables are alternating combinations of _, i, l and o. It makes it all but impossible for a human to understand, but does serve to convey a point ... most "objects" (objects meaning a thing, like variables, parameters, command options) are used by the software in context to the statement. So, the only ambiguity which might exist is in/for/to the developer. Given that, I would argue such ambiguity is of extreme concern for many reasons (including software maintenance), and all such confusing notions should be avoided and re-coded when encountered.

>Which is not so severe as for those people who declare this to a project which does not apply to the (project) namingconvention.
>And yes technically speaking it is correct to program strtofile('m.txt') so technically speaking he made a point.

My favorite was the example:
create cursor _screen ( width i, height i)
insert into _screen (width, height) values(500,500)
browse.

A fascinating insight into VFP's object/table/cursor/memory subsystem.

Best regards,
Rick C. Hodgin