JVE>   JVE> Hi,
 JVE>   JVE>   My question: Is OS/2 a mission to code or not ?

>I don't understand the question.

 JVE>  How hard is it to write a program for OS2 compared to
 JVE>  Windows ?

If the programmer has no previous knowledge of either,  writing an OS/2
program is ___much___ easier.

The OS/2 api is Microsoft's second try at designing an API.  All versions
of Windows (incl 95 and NT) are still based on their first try.

Just the names of the Windows functions themselves are easly confused with
your own (or other's) functions,  for example:

 CreateWindow
 Beep
 ChooseFont
 GetMessage
 IsWindow
 SetWindowText
 CreateBitmap
 LoadBitmap


Believe it or not,  these are actual system call names.  If you were
reading some code using them,  there is no clue as to what is a system call
and what is not.

Below are the os/2 counterparts,  which have a three letter prefix to make
them easily identifiable.  The API also follows strict naming rules;  most
of the time,  you can find a function by "inventing" the name.

 WinCreateWindow
 WinAlarm               (or DosBeep() for non-pm programs)
 WinFontDlg
 WinGetMsg
 WinIsWindow
 WinSetWindowText
 GpiCreateBitmap
 GpiLoadBitmap




--- Maximus/2 3.00