Looking for Windows C++ Guru for h*elp

Sandy sganz at wgn.net
Mon Feb 9 04:18:43 GMT 1998


At 02:35 PM 2/8/98 -0800, you wrote:
>Tony,
>
>Aside from being a rather old technology, the OWL run time is going to add
>a LOT of
>code to you executable module.

Not as much as MFC imposes with either compiler, OWL makes things much
eaiser then _any_ of the crap that you have to deal with MFC, but OWL
itself is not the tool to be using. The issue is not at all the compiler,
but the framework that you use, and from a programmers standpoint MFC is
the worst, OWL is better, and the VCL style that you get with C++Builder or
Delphi really blows them both away. The VCL was created from what the
developers learned what was wrong with both MFC and OWL frameworks. VCL can
pretty much do what ever you need it too, and without all that SDK or
(Object wrapped SDK in MFC's Case) BS.

Spouting some 2 Cents

Sandy

>
>You might find some of the more recent compilers from Microsoft and Symntec
>to be a better
>fit. They will also let you use the most up to date features found under
>windows 9x.
>
>My 2 and a half cents
>Daniel
>
>
>
>
>
>Tony Cooper wrote:
>
>> Hi all,
>>
>> Sorry if this seems completely off subject, but does anyone know (And I
>> mean really) know
>> how to program C++ using Borland OWL under Windows, that could help me
>> with some
>> really tricky bits. Somewhere between User and expert is the level of
>> help I need.
>>
>> email direct please.
>>
>> Thanks in advance
>> Tony
>> --
>> Sent By Tony Cooper.
>> email: tony.cooper at virgin.net
>> Allow at least 10 working minutes for reply. ;)
>
>
>
>



More information about the Diy_efi mailing list