Hi Mike,
>If I were on the VFP team (there goes the neighbor hood ;-), I would have made WITH a compile time function; adding whatever the WITH is when it compiles, so there is no over head (except for when it compiles of course :-)
If I understand what you mean here, this would defeat the purpose of WITH...ENDWITH. The construct means that it's unnecessary to traverse the object hierarchy to see which object you're talking about. VFP loads the target object into memory (or whereever, I don't profess to know the gory details). The point is that not having to start at the top of the hierarchy and walk down through the dots saves heaps of time. Adding the WITHed object at compile time puts the overhead back into the equation.
>
>I also would have added an implicit WITH THIS to every fucntion, but thats just me :-)
You're a VB wannabe < gd&r >
Cheers,
Andrew
If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?
From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."
All my FoxTalk and other articles are available on my
web site.
Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
