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

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Who Wants To Be Logical? I Do! I Don't! (with Claude)

In my book, Towards Consciousness, I explore PET , a theory that attempts to explain consciousness and possibly how it might apply to AI. As part of the conversations with AI series, I've included this conversation with Claude.AI in which we were talking about something very different and yet the conversation redirected itself back to PET. For the record, there is no such thing as "Colfsity". A It's interesting to me that people want to proclaim their distinction from being rigid and unlike machines, yet they also complain that the "best" people keep a rigid schedule, regular routines and logic understanding of issues. That's a perceptive observation about a real tension in how people think about themselves and what they value. There does seem to be this paradox where rigidity is simultaneously rejected as "robotic" or inhuman, yet praised when it appears as discipline, consistency, or logical thinking. I think part of what's happening is t...

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 distinction...