From: "Yuri Prokushev" <[EMAIL PROTECTED]>
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Date sent: Sun, 07 Jul 2002 21:51:06 -0400 (EDT)
Priority: Normal
Subject: Re: [Sibyl] first alpha of the new bsedos/doscall
Send reply to: [EMAIL PROTECTED]
> > ??? What do you mean with this? Have you tried to compile e.g.
> >basicpm.pas with -WG?
> Grr... In docs no any info (this option documented as win32 target).
Sorry, you're right. :-( But at least ppc386.exe without parameters
shows you an equivalent switch -Dw with a proper comment. Anyway, I
wanted to have this common for OS/2 and Win32, that's why I added
support for both -WG and {$APPTYPE GUI}directive (and added the
missing {$APPTYPE FS}) under OS/2 as well. I'll probably remove -Dw
from FPC 1.1 altogether. But it should be documented, that's clear.
> After compilation I used emxbind .... -s -p for PM apllication :). Ok.
FPC uses emxbind as well (it just adds the appropriate option when
calling emxbind to create EXE file from a.out file created by ld).
> >> ??? You using doscalls/pmwin like stuff but don't want use other
> >> standard things? Strange....
> > DosCalls / PMWin are _system_ libraries, not C compiler libraries!
> I consider any library is system if distributed with OS.
I (and the other FPC core team members) don't. DosCalls and PMWin
form parts of the OS/2 API. Libc doesn't. Some libc is distributed on
almost all platforms nowadays, but that doesn't change anything on
the fact it still isn't a system library. You can have several libc
versions running on top of one system (in the case of OS/2 there's
EMX, VACPP, Watcom, Borland, ...).
> >> Wait, wait... I don't talk about emxlibc. I'm about native libc.
> > ??? Which "native" one do you mean? Libc from VAC++?
> LIBCM/LIBCS in os2/dll.
> ------------------
> The C-runtime DLL's shipped with OS/2 V4.0 (and above) are XPG4
> compliant. They are based upon the source code to the VisualAge
> C++ rutimes, but are modified to use OS/2 internationalization.
> The DLL's in question are:
> \OS2\DLL\LIBCM.DLL - Multi-threaded library
> \OS2\DLL\LIBCS.DLL - Single-threaded library
> \OS2\DLL\LIBCN.DLL - Subsystem library
OK, I see. I wasn't aware of these, but that doesn't change much
anyway - they are still nothing more then (modified) VACPP library
files distributed together with OS/2. In addition to what I wrote
above, these files aren't available on OS/2 Warp 3.0 at all as you
noted yourself. BTW, how much code would you really save if using
these? Do you think it's really worth the trouble with creating and
maintaining two versions of RTL functions?
Tomas
-----------
To unsubscribe yourself from this list, send the following message
to [EMAIL PROTECTED]
unsubscribe sibyl
end
