Skip to main content

Learning VFP 102: Scope

Craig Boyd just posted his Learning VFP 102 : All about Scope (not the mouthwash), he also discusses arrays.

Great stuff Craig!

One of the things I wish he had for this was a "take-away" or some kind of call-out that popped out on top to tell people what he was saying about important rules. Sure he gives out the source code but cheat sheets would be really helpful!

One note: great example for using DEBUGOUT.

So I'll start doing some on these take-aways. Although you may also want to refer to Andy Kramek's two part article as well.

Part I

His Guidelines
1. Stay away from public variables. Use screen properties instead for global objects or create a property on your form. Try and avoid them.
2. Also avoid private variables. (huh? - and he really didn't explain why.) Ah - he did mention on the side - send them as parameters instead.
3. Always remember to declare your variables. Just because you can, doesn't mean you should. ( I just did a screen cast with Ed Leafe about Dabo where they don't call them non-strongly typed variables, they call them "Dynamic" instead.)
4. Use Local Arrays. If you need to share arrays, don't use Private - send it in as a parameter. Ah, Andy Kramek had a better suggestion a while back - pass it as an object!


One other suggestion - run the online on a high resolution - I was set to 1024x800 and I still couldn't see it well at all. The videos are available online and in SWF format.

Comments

Popular posts from this blog

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator)

So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinctions I…

Security in Windows 10

http://www.slate.com/articles/technology/bitwise/2015/08/windows_10_privacy_problems_here_s_how_bad_they_are_and_how_to_plug_them.single.html

 discusses some Windows 10 privacy settings and their implications.

"Finally, we will access, disclose and preserve personal data, including your content (such as the content of your emails, other private communications or files in private folders), when we have a good faith belief that doing so is necessary." "In other words, Microsoft won't treat your local data with any more privacy than it treats your data on its servers and may upload your local data to its servers arbitrarily"
I did a quick install on a VM choosing the Express settings. When I fully deploy this on a real workstation, I will likely choose to wade through all of the individual pages, as David recommends.

Of course, losing one's privacy is nothing new - it's happening all over the place (despite Santa Ana's police force's lawsu…

AppleSoft

I'm not TRYING to be "fanboy-flame bait" but what I saw yesterday was a typical "Do it this way, now do it this way and then we'll go back to this way" all over again.... a move similar to what Microsoft does to developers on an ongoing basis.

Remember the first iPhone? Smooth and curved, at least as far as it could be back then. I still pull out my 3G and can see the curves on it.

Then the 4 came out and "boxy" was all the rage. Everything should be "tight with corners"

Now iPhone 6.... smooth and curvy is back. Granted I don't have the actual device yet, but that's the message.

Guess that means the iPhone 8 will be back to boxy.

And honestly, Apple Watch is not worth "one more thing" --- especially when everyone knows it's going to be shown. "One more thing" would be something no one saw coming.  The device itself ? Very interesting and yes, definitely lots of potential but "one more thing" wor…