Advantages/disadvantages Visual C++ <-> Borland
Mikael Grehn
The classical question: What are the advantages using Visual compared to using Borland Builder and what disadvantages are there? I know the graphical component support is much better in builder but
that the code insight sucks in Borland.
What else? A "Visual advantages" and "Visual disadvantages" list would be great.
--
mvh
Mikael
CvN
If you are doing an app that is highly visual with many complex user
interfaces, then there is no choice. BCB is much better and development time
will be greatly decreased. If the app is not that visual, the VC++ is quite
good.
Craig.
Mikael Grehn <mik...@envilogg.se> wrote in message
news:39DAEE5A...@envilogg.se...
Matt T
Mikael Grehn <mik...@envilogg.se> wrote in message
news:39DAEE5A...@envilogg.se...
> Howdy!
>
> The classical question: What are the advantages using Visual compared to
using Borland Builder and what disadvantages are there? I know the graphical
component support is much better in builder but
> that the code insight sucks in Borland.
>
> What else? A "Visual advantages" and "Visual disadvantages" list would be
great.
From what I have heard from users:
BCB is faster for creating projects, and is truly visual, but has problems
when used for very large projects.
MSVC is not really visual as BCB is, but does not fall apart at the seams
for larger projects.
BCB is not compatable with the DirectX8 SDK so any DirectX programming is
out.
MSVC is compatable with DX8, has MFC, and seems to be used more in examples
and books on Windows programming. So when you want to learn about
something, having the right compiler that matches the code examples really
helps.
When comparing the basic versions of BCB and MSVC, MSVC has more quality,
more options.
MSVC is more predominately used in the industry, so when you want a job
programming it will help to know it.
I have heard that large BCB5 projects sometimes develop memory leaks in the
finished product.
(This could be a code issue - programmer's fault, or maybe not...)
I recently compared both, and decided that I liked MSVC better because it
fitted what I wanted to do;
which is create Windows programs using API, DirectX, and if I want the
option of MFC - I have full compatability.
I do like Borland's products, I have BC++5.02, TurboC++3, Tasm4 (all work
fine); but I don't think
that Builder really offers me an advantage. Speed is nice, but so is a
solid compiler - which I don't think
that Builder really is just yet. Maybe when version 6 is out it will be
better. There are definately issues with Builder5 that have yet to be
addressed by Borland.
I have noticed that MS does address user issues and fixes many of them
through the release of service packs to upgrade VC6. I feel that MS is more
focused on this, and they don't let it drop, even while they continue to
develop the next version of VC. This is important and qualifies as a good
reason to go with VC6.
From a financial point of view, I like MSVC6 standard better than BCB5
standard.
VC6 has more features in its basic version than BCB5.
In the Pro versions BCB5 appears to be ahead in features, especially when it
comes to debugging.
However, certain product flaws work against smooth compiling, nullifying the
advantage in my opinion.
The vanishing IDE situation is not desirable.
I weighed the options and picked MSVC6 because it seems to be built better
and had the features I wanted.
The pro version would have been a little more desirable, but I decided to go
cheap for now.
When I get better at Win programming then I can upgrade. :)
I have been using it for a while now, and really like it.
The help feature has a nice interface, good definitions of functions/code -
good quick reference.
Hope that helps you decide,
-Matt