Hier was Leif Erik Larsen meint -
-----------------------------------------------------------
Hi,
yes it is true that Larsen Commander is compiled with IBM VAC++ 4, but
it is not true that I do the development in general under it. I just
use the command line compiler (project builder). My experience with
IBM VAC++ 4 is that the IDE is slow and very unstanble. Therefore I
don't use its IDE at all. Espessially the debugger is extremely
unstable and it freeze the OS/2 system very easily, at leats when it
comes to multithreaded applications like Larsen Commander. Happily,
the VAC++ 4 compiler can produce debug information that is compatible
with the debugger in VAC++ 3.6, so I use that debugger instead. Even
if it looks somewhat odd. It works at least. And it is stable.
When it comes to the VAC++ 4 compiler it self, mye experience is that
it is quiet stable and fast enough, but it seems to produce some buggy
code when compiling with all code optimizations on. Larsen Commander
for OS/2 is therefore compiled with some code optimizations turned
off, but for this kind of applications this is no harm. The command
line interface of VAC++ 4 also works quiet stable, and as I said this
is really all that I use of the VAC++ 4 box.
Note that all my comments here regards to the OS/2 version of VAC++ 4
only. I have no experience with VAC++ 4 on Windows. On Windows I use
Borland and Microsoft products.
I don't know of any non-outdated C++ IDE on OS/2 that works stable
enough (I need support for the latest ANSI C++ syntax standards, so
Borland C++ on OS/2 is no option). Due to these facts my OS/2
development is rather command line oriented.
When it comes to Windows, however, I have found several IDEs to my
pleasure. Both MinGW, Borland C++ Builder and Microsoft .NET suites my
needs. I have ended up with Microsoft's alternative in my daily IDE
oriented development, because in my optinion it is simply the one that
works best and most snappy. But the fastest command line compiler is
Borland C++ 5.5! This one is free too. Borland C++ 5.5 on Windows
compiles my project in seconds, while IBM VAC++ 4 on OS/2 needs
several minutes, even if hardwate is the same.
I look foreward for the open source Watcom C++ compiler to get support
for all the latest ANSI C++ syntax standards. Then I can (hopefully)
compile for Windows when in OS/2 - and vice versa, which will be just
great!
BTW, I don't know any other user of IBM VAC++ 4 either. ;-)
Kind regards
Leif Erik Larsen
-----------------------------------------------------------
[ Leser: 56 ] |
![[Forum]](../../../images.os2.org/de/forum.gif){kind=small}
![[Forum]](../../../images.os2.org/de/forum2.gif){kind=small}
