🚀 go-pugleaf

In article <ejgc6HMyEHA.3120@TK2MSFTNGP12.phx.gbl>,
 "Filip Konvicka" 
 <filip.konvicka.remove_this_antispam_token_please@logis.cz> wrote:

> Jason,
> 
> personally I think that the "simply-set-a-member" approach is rather
> confusing, and indeed delphish. A single assignment looks as though it is an
> atomic operation, but it is in fact calling a cascade of functions... in my
> opinion this leads to much less efficient code, because you re-read or
> re-set the attributes more often (instead of caching the values). Not only
> that - the example you provided suggests that instead of calling 1 function
> to set window position, you do 4 "assignments" (which are no doubt
> implemented by calling the aforementioned function 4 times!) But, all this
> is just my opinion. I think that it's a good thing for you to learn the
> WIN32 API or the (more or less thin) MFC wrapper so that in the end you can
> use the API more efficiently. In VC++, I think that you have no other choice
> anyway :-)
> 
> Best Regards,
> Filip
...

Hi, Filip, and thanks for the reply.

I certainly don't have problem with non-delphish approaches or with 
making a single call with multiple variables rather than several 
individual assignments if that's a more efficient way to do things.  I 
just like the idea of everything involving member functions of a given 
object like someComponent->SetPosition(x,y,width,height), for example.

Another poster (who I'll reply to next) showed an example I found quite 
nice in which he created a CEdit object and called its member functions 
to play around with its settings--not too bad from my perspective (at 
least with that example).


-Jason