You bring up a "favorite" "issue" that I have with MS generally and the VFP team in particular...

MS consistently lets MSKB Articles that provide 'working as designed' but with clearer explanations or 'How to...' because the documentation obviously isn't sufficiently clear for too many people be the end of the line when in fact the last step should then be to ensure that the proper documentation is updated.

Still leads me to believe that VFP loses many many newbies for the simple reason that it is all too complicated/flaky because of MISSING documentation.

How much effort would it really have taken to update the base documentation after publishing a KB article?!?!?!

cheers


>Fabio,
>
>I agree with Thomas, it's not a bug in the product. However this behavior isn't documented in the help. It's mentioned in How FoxPro Passes Parameters to Subroutines mskb #Q101025, though. Feel free to submit documentation errata.
>
>>Previous issue Thread #951922
>>
>>Bug/Issue : 3 of 27
>>
>>TITLE: Bug: call by Reference hide Public and Private variables
>>
>>VERSION: 09.00.0000.1720 and previous
>>
>>STEPS TO REPRODUCE:
>>

>>clear
>>PUBLIC myvar
>>myvar = 'i want see this'
>>ON ERROR ? MESSAGE()
>>? ABRA(m.myvar)
>>? ABRA(@m.myvar)
>>ON ERROR
>>
>>PROCEDURE ABRA (pVar)
>>RETURN m.myvar
>>RETURN ' -> BUG '
>>

>>
>>OBSERVED BEHAVIOR:
>>When the call by reference is made, VFP hide the external PUBLIC and PRIVATE variables
>>
>>EXPECTED BEHAVIOR:
>>VFP does not have to hide these variables.