Thread: Borland Turbo C++ 3.0 config

Visual Studio Express. Comes with PCH. Makes your life easier when working with Windows.h.

What's PCH? and what about sql.h? does it support it or will I have to install it (some way, some how)?. Thanks for your reply.

In this particular case, PCH stands for Pre-Compiled Headers - it's also short for Pacific Coast Highway for example, but that makes no sense in Elysia's comment.

I'm personally not a great fan of Pre-compiled headers, but that's up to you.

What does make sense is to use a compiler that actually supports Windows well - and whilst Turbo C allows you to compile windows executables, I would say that it's not exactly "state of the art" when it comes to compatibility with standards and functionality you expect from a modern compiler.

Also, I'm 90% sure that conio.h only works in DOS-mode, which in turn means that you can't actually use chunks of memory that are bigger than 64KB - which may restrict your ability to work with databases - at least if the database contains a fair amount of data.

--
Mats

PCH is a great feature that allows the compiler to pre-compile certain headers. That means every time you build your project, it won't have to re-parse all those headers, which can significantly speed up compile time, especially with big headers such as Windows.h which includes a multi-tude of other headers.
Visual Studio is also a great IDE in sense that it has a great debugger and is a very feature rich IDE.

Nothing beats cmake, vi and gdb

Not a fan of VS, however I do think it's very nice (so long as I'm not using it ) -- give it a whirl you'll probably like it.

The nice thing with Visual Studio is that it's a professional tool aimed at professional developers. As such, it has many very nice functions including debugging without having to type anything in a command line aka gdb.
No need to remember commands and much faster than typing if you need to. Also has very nice features such as hovering over a variable allows you to see all the contents of it. If it's a class, you can browse through its members, for example. If it's a linked list, you can browse through your next/prev pointers in infinity to see if the list is intact.
Not to mention you can set data breakpoints which allows the debugger to break if a certain memory location was read/written or changed in any way, including a condition as to when it should break if an abovementioned event happens.
Of course it works with line breakpoints as well, which allows you to break on a specific line, and include a conidition to break if, say, i == 50 (useful to break after X amount of loops in a loop, for example).
It also includes a memory viewer to monitor what is happening to memory. That's useful, too, sometimes.
There's a lot in Visual Studio.

Now, while gdb and GCC is free, it is not a child's tool or an amateur's tool. It can be used as a professional tool, as well, but Visual Studio was developed specifically towards professional developers while gdb was not - it was designed for everyone.
That is also not to say command lines are not for professionals - but in Windows, GUIs are often considered more productive than command lines unless they are used for a specific purpose. We could go on about that forever, though...
Now I'd like to see gdb beat that

The nice thing with Visual Studio is that it's a professional tool aimed at professional developers. As such, it has many very nice functions including debugging without having to type anything in a command line aka gdb.

If you did not notice, you are implying that only amateur developers use the command line or develop command line oriented tools.

My bad. Visual Studio was aimed at professional developers, while gdb is aimed at everyone, not limited to just one. It is in no way just an amateur tool.
Command line tools have their uses, but in Windows environment, everyone works (mostly) with GUIs if it can be helped.
Gdb isn't bad, but seeing as it's developed under linux environment (I think), it's command line. Most things that are developed under linux seems to do. It's like a trend, from what I understand. But I am no linux dev, so what I see may vary from the actual truth.

> Visual Studio was aimed at professional developers, while gdb is aimed at everyone,
Yes... that explains VS Express. Not.

> Now I'd like to see gdb beat that
There are a few GUI front-ends to gdb, valgrind etc. No-one says you have to use the CLI...

> It's like a trend, from what I understand.
Usually, however it's an advantage as far as I'm concerned (I have a Linux box in my cupboard I use for compiling/cross-compiling, debugging, svn, etc). And there's usually GUI front-ends to most of the tools.

Originally Posted by cpjust

Visual Studio is also free. Well, the "express" version at least.
If you can get a professional tool for free, why bother with others?

I think it's great that you can get a professional tool for free since they do tend to be expensive and usually good!

As for Pre-compiled Headers... If they're enabled, the first thing I do is disable them. They always @#$! up my builds!

Doesn't that mean you just don't know how to use them? I never had a problem with them, or very few at the least.

Though I might add:
With Visual Studio being a "professional" tool, I mean that it is very feature rich, has a very good debugger, etc. Professional as in much features. It doesn't mean it's better than anything else. It just means that it was developed for professional developers in mind - to meet their needs.
GDB and the rest was developed for free for all programms, so their aim isn't quite the same, but that doesn't mean the functionality isn't there. It's a matter of preferance in most cases.

I'm not willing to let this turn into a flame war