There is a very thin line between declaring and assigning a value to a variable.

In VFP

x = 1 && Declare and assing x to 1 (declared as private)

IN C#

int x = 1; // Declare and assing x to 1 (declared as local)

what is different ? both language can declare and assign on the same statement, is it bad practice ? IMHO it is not, the bad thing is that x is declared private in VFP.



>I don't agree with this new SYS () function as it would support not declaring all variables used by a given function which is a bad programming practice IMHO. You can use _VFP.LanguageOptions to force the declarations of variables.
>

Define Class Test As Session
>
>	Protected Function Init()
>		_VFP.LanguageOptions = 1
>	EndFunc
>
>	Function Test1
>		x = 1   && Error
>		? x
>		? This.Test2()
>	EndFunc
>
>	Function Test2
>		Return x && Error
>	EndFunc
>	
>EndDefine

>
>

Define Class Test As Session
>
>	Protected Function Init()
>		_VFP.LanguageOptions = 1
>	EndFunc
>
>	Function Test1
>                LOCAL x
>		x = 1   && OK
>		? x
>		? This.Test2()
>	EndFunc
>
>	Function Test2
>		Return x && Error
>	EndFunc
>	
>EndDefine

>
>>I don't beleive you got me right, my wish was to have a new sys() function to changed the default behavior of VFP from creating all undeclared variable as LOCAL to the function declaring it:
>>
>>Current behavior:
>>ox = CreateObject("Test")
>>=ox.Test1()
>>

>>Define Class Test As Session
>>
>>	Function Test1
>>		x = 1
>>		? x
>>		? This.Test2()
>>	EndFunc
>>
>>	Function Test2
>>		Return x && x is private so no error here
>>	EndFunc
>>	
>>EndDefine
>>

>>
>>New Sys() Option
>>
>>

>>ox = CreateObject("Test")
>>=ox.Test1()
>>
>>Define Class Test As Session
>>	
>>	Protected Function Init()
>>		=Sys(9999, 1)  && New sys function
>>	EndFunc
>>	
>>	Function Test1
>>		x = 1
>>		? x
>>		? This.Test2()
>>	EndFunc
>>
>>	Function Test2
>>		Return x && x an error here, x is local to test1()
>>	EndFunc
>>	
>>
>>EndDefine
>>