It would expose to you an error where you forgot to initialize a  
variable. If you are debugging and you see A5A5 it will trigger your  
memory to tell yourself "hey, I forgot to initialize that variable! No  
wonder my program is acting weird!"

I don't know if it affects string variables, but it would be easy to  
test.

On Apr 1, 2008, at 12:53 AM, Robert Covington wrote:
> I've always wondered what the heck that pref
>
> "Fill local variables with 0xA5A5 to expose programming errors"
>
> meant.
>
> What is 0xA5A5? and how's that supposed to work? Any var? Or just  
> string vars? (I'm clueless, and there aren't any help tags in the  
> editor prefs)
>
> I had a report of a bug in my last version of Compositor, somehow a  
> movie rectangle was coming out with some 8096 sized rectangle (But 0  
> on the other dimension), never happened in like 6 years or more, and  
> only think I can think which would have broken it was something like  
> a changed compile setting with that enabled?
>
> Anyhow, I added a Clear Local and now things set correctly from the  
> getgo when I check for a default from the GetPictInfo sourcerect vs  
> the local, but ...
>
> Robert