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

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

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

I’m Supposed to Know

https://programmingzen.com/im-supposed-to-know/ Great post for developers who are struggling with unrealistic expectations of what they should know and what they shouldn't. Thirty-forty years ago, it was possible to know a lot about a certain environment - that environment was MS-DOS (for non Mac/UNIX systems). . There was pretty much only a handful of ways to get things going. Enter networking. That added a new wrinkle to how systems worked. Networks back then were finicky. One of my first jobs was working on a 3COM + LAN and it then migrated to LAN Manager. Enter Windows or the graphical user interface. The best depiction of the complexity Windows (OS/2, Windows NT, etc) introduced that I recall was by Charles Petzold (if memory serves) at a local user group meeting. He invited a bunch of people on the stage and then acted as the Windows "Colonel", a nice play on kernel. Each person had a role but to complete their job they always had to pass things back to h...