Yes and he is actually a good programmer.

>Do you know, what happened with the original programer? Is he still programming? :)
>
>>It's not the worse way to name variables. I supported an application where original developer used variavbles name like m.f*ckyou and user would call and complain that program is cursing her. It turned out that she got message "Variable 'f*ckyou' not found".
>>
>>>>>
>>>>>Before Nancy's explanation I thought, that it's an short form of "function". Anyway, I personally hate to see all these "foo"s in my colleague's code. I always use a meangful name for variables, objects, etc., even for temp variables.
>>>>
>>>>
>>>>
>>>>Nadya,
>>>>
>>>>You mean that they actually use FOO and BAR in real live code!!!
>>>>
>>>>Even *I* wouldn't do a thing like that.
>>>>
>>>>Cheers,
>>>>
>>>>Chris
>>>
>>>Don't remember about BAR, but FOO - definitely... Something like FOO=&CallProc
>>>Another problem is, that not all variables are declared. This also contradicts with my style, because I declare each used variable explicitly (though it's unnecessary). I also use l+type prefix, thought this is also obsolete, becase I also use m. to distinquish vars from table fields...