Louis, I'm afraid that Jan Van Eden was wrong on several points.

JVE>
   >  Visual Age - an IBM product, this means...
   >
   >  1 - You can only write applications for OS2 or IBM related O/S
   >  2 - Only IBM supported database engines are allowed, i.e: DB2
   >  3 - Poor product documentation and no 3rd party books.
JVE>

   Firstly, let's make it clear that when people refer to "Visual Age",
   they are usually talking about VisualAge SmallTalk.  IBM has a whole
   "Visual Age" family of languages (C++, SmallTalk, CoBoL, and BASIC).

   I cannot comment on the documentation, not being a SmallTalker, but it
   seems unlikely that only one database engine is "allowed".  It's a
   pretty fair bet that VA SmallTalk can call most third-party libraries.
   In which case there's a wide range of database engines available.

   Later in his message, Jan talks about "both products", implying that he
   is talking about VisualAge C++.  The above comments are *definitely*
   untrue for VA C++.  VA C++ is available for OS/2, Win32, AS/400, and
   AIX.  It can call *any* database engine.  And there's a wide range of
   good quality books and documentation available.  Just look at the
   booklist that I post here regularly.

JVE>
   >  Visual Age C/C++, does have a very powerfull compiler, but the GUI
   >  design tools they can - I`d rather not say..... A very nice tool
   >  to develop system DLL`s and stuff with, but don`t try to write
   >  a GUI application. Your learning curve for this compiler is about
   >  6 months to 1.3 years.
JVE>

   Jan forgets to state that you don't *have* to use the Visual Builder to
   create applications.  Indeed, there are other application generators on
   the market (I would have recommended JBA Guidelines, but JBA has ceased
   development on it.  Try Prominare Designer instead.).

   I personally just use a text editor, which works fine for me.  And,
   incidentally, I have no trouble writing GUI applications in C++.

   The idea of a learning curve for the compiler is also somewhat flawed,
   since he's (probably) really talking about the learning curve for the
   C++ language and (possibly) the Visual Builder.  Any experienced C++
   programmer will find little to no trouble coming to grips with the IBM
   VisualAge C++ *compiler* -- or, indeed, any of the other four C++
   compilers for OS/2.

JVE>
   >  Visual Age Basic, don`t even bother looking at it! It does have
   >  compatability with Visual Basic V3 applications, [...]  And it is
   >  well known as a slowdown tool. Applications require at least 90
   >  seconds to start up.
JVE>

   Speaking as someone who had to use BASIC at one time, I believe that
   it's fair to say that BASIC as a whole is a "slowdown tool".

JVE>
   >  In conclusion - both products require at least 16meg of memory
   >  and this means that your distribution applications also require
   >  machines with 16meg, but don`t worry: it`s not documented anywhere!
JVE>

   The second part of this sentence is complete rubbish, of course.  The
   memory requirements for the *compiler* don't have anything to do with
   those of the resultant application.  Being a programmer yourself, I'm
   sure that you are well aware of this.

   Incidentally, Jan is showing that his actual experience of VA C++ isn't
   very great here, since anyone who just has the box that the compiler
   came in will know its memory requirements ... since they are printed on
   the side.

JVE>
   >  1. You can either consider writing an OS2 application in Visual Age
   >  C/C++ using resource editors, and that crap, taking you at least
   >  5 months.
JVE>

   Again, as a programmer yourself, you probably realised straightaway
   that this is rubbish as well.  You can write a small simple program in
   an afternoon, and a large complex program in a year.

JVE>
   >  2. You can evaluate another compiler, so far the best compiler for
   >  OS2 I have ever seen is Speed Pascal, it`s brilliant!
JVE>

   And I'm sure that you are well aware that this is more apples and
   oranges rubbish.  Speed Pascal and IBM VisualAge C++ implement two
   different languages, after all.

   Having said that, I happen to remember that you are a Pascal
   programmer.  In which case, take a look at both Speed Pascal/2 and
   Virtual Pascal for OS/2.  They both have "demo" versions, which you can
   snaffle from any halfway decent files site.

   > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 3.01