[Skinner]

I want to start using WinAPI in my programs and I am using Borland RadStudio2007. All pdfs I have on this subject are based on VisualC++ - and Borland apparently used to use something called OWL. Is there a simple way of using WinAPI in Borland's compiler or am I better off using Visual C++?

Thanks.

[Amadeus]

There should be no problem using a borland compiler to compile WinApi programs, as long as everything is linked properly.

[Skinner]

Amadeus, on 21 Jul, 2007 - 08:42 AM, said:

There should be no problem using a borland compiler to compile WinApi programs, as long as everything is linked properly.

OK but in the manuals I have on WinAPI it says compile a Win32 application - in RadStudio C++ Builder I am using there is no option for this, only console app, VCL app etc. What should I be using?

[corliss]

Hey guys,
I was taught using borland due to my teachers not wnat ing to be a mirosoft kiddie but I am now using vs 2005.
I would say stick with visual studios.
cheers

[Amadeus]

I'm not a borland user, so I'm not familiar with all the compiler options - what are they again?

As for sticking to VS, I'm not sure I'd want to limit myself in that manner.

[no2pencil]

The purpose of Win APIs is that you can use your code in any environment. I've actually ported some of my code from C++ to ASM, & the APIs will still take the same arguments. So I don't see any problem in changing IDEs. One draw-back to using Windows APIs is when versions of Windows are released, if the API arguments change then you're program will need to updated to detect the version & adapt to the change as well.