Re: Is VS2008 a good environment?

I think you're a bit confused.

Windows provides you an API called Win32 for usermode applications. The API
goes with certain ABI (application binary interface) best suited for
programs written in plain C language. It can be cumbersome to write GUI code
with plain API, though.

To facilitate RAD, different vendors (including MS) provide different
wrappers and languages, including Delfi, VB, MFC, Qt. Those allow you to do
your programming in kind of OOP style.

Making a shim between "static" function and a proper member function is very
trivial exercise. If you mind that, MFC and Qt already do that for you. It
would be a mistake to blame Win32 API for that.

Again, Win32 API (not Visual Studio 2008) provides you C API and ABI. It's
up to you or a framework you choose to add convenience and syntactic sugar.
Use MFC or some other library.


"me4dtrade" <me4dtrade@xxxxxxxxx> wrote in message
news:4c106b2b-3242-4a42-ad3c-6aada89c92f6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
First I admit that I am pretty new to VS, even though I have many
years' experience in other languages and environments.

Upon programming VS2008 using win32 and C++, I find that it is not
straight forward to do lots of things. And most of the problems are
pretty basic.

For instance, if you want a nearly complete OOP, you need to create
your own AppWin class that is used as a container of everything. You
can include all other classes in it and do everything. That is, AppWin
is a factory that includes all mathinary and tools and workers to
produce certain products. But there are problems.

For instance, the default WindowProc which processes messages has to
be defined STATIC, which makes everything difficult because you can
not use non-static (instance) members in the function. You have to
tweak it and turn it into a non-static function. Why? Why M$ doesn't
do this for our programmers automatically? Pretty stupid M$. And it is
against OOP logic.

The other thing is that implementing thread to a member function is
not straight forward, either. And again you have to tweak it to make
it to be able to use non-static members.

Every windows app needs to process messages, nearly every windows app
needs to have their threads, and non of these are straight forward in
VS. Isn't it stupid?



.

Relevant Pages

  • Re: serielles Modem ansprechen ( AT Befehle )
    ... Falls das Modem korrekt bei Windows angemeldet ist, ... dann Verbindungsaufbau im Prinzip über das Win32 'TAPI' API (siehe MSDN) ...
    (microsoft.public.de.german.entwickler.dotnet.csharp)
  • Re: LoadLibraryEx (as datafile) and MorIcons.dll - extracting icons
    ... At the time the documentation for Windows 2.x was written there was no ... publicly available Win32 API or SDK. ... In my copy of the 16 bit SDK that cam ...
    (microsoft.public.win32.programmer.tools)
  • Re: Suggested base class additions
    ... If you think of Dolphin as primarily a Smalltalk-flavoured front-end to Win32, ... then it'd seem quite natural to have all the API wrapped/exposed. ... on Windows, then the less you see of the Win32 cesspit the better. ...
    (comp.lang.smalltalk.dolphin)
  • Re: May I introduce myself to cobol?...
    ... a clarification on what the win32 API ... meaning "Application Programming Interface", ... in the context of the OS Windows ...
    (comp.lang.cobol)
  • Re: newbe about API
    ... Emne: Re: newbe about API ... > I found all these API-CALL strings are finally compiled to ... more than that...and Windows simply takes this to an extreme that this ... DLL, when a weak point is found (which, with Microsoft, is something ...
    (alt.lang.asm)
Loading