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

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

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

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP