JM>
  > I have the Borland C++ for OS/2 compiler.  I am considering
  > doing some SOM programming.  I see someone saying that you
  > can compile the SOM part using a SOM compiler in OS2
  > Toolkit (which I do not have) and submit the output to the
  > Borland compiler.
JM>

  You can, theoretically, use SOM with Borland C++ 2.0 for OS/2.

  However, you must purchase the SOMObjects Developers' Toolkit for OS/2
  in order to do so (see the Pros and Cons list Glossary for more
  details, including part numbers), which includes the various header
  and library files that are required, and the "SOM compiler" that
  translates class definitions written in IDL into C and C++ SOM
  language bindings.

  Whether those bindings will work properly with Borland C++ 2.0 for
  OS/2 is also open to question.

  Personally, having used DirectToSOM C++ in IBM VisualAge C++ 3.01 and
  MetaWare High C++ 3.32 I would *strongly* recommend to someone who
  knows the C++ language and who wants to start using SOM to use a
  DirectToSOM C++ compiler.  It's by far the easiest way to use SOM, if
  you are proficient in C++.

  This is a SOM class in DTS C++ :

      class A : public SOMObject { } ;

  Admittedly it's a trivial class, but it does highlight the point that
  defining a SOM class in DTS C++ need be no more difficult than
  defining a C++ class. It does get slightly more complex if you want to
  use SOM features that have no equivalent in C++, such as metaclasses
  and release orders, but not very much.

  DTS C++ certainly compares *very* favourably against using the C
  language bindings for SOM, which define an enormous number of macros
  to make things work and cannot easily handle using the same name in
  different scopes.

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