From:                   "Yuri Prokushev" <[EMAIL PROTECTED]>
To:                     "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Date sent:              Sat, 29 Jun 2002 14:25:01 -0400 (EDT)
Priority:               Normal
Subject:                [Sibyl] first alpha of the new  bsedos/doscall
Send reply to:          [EMAIL PROTECTED]

> First alpha of the new bsedos/doscalls commited...

 I've shortly looked at it. I appreciate you have listed corrections 
to FPC sources in a standalone file, that will definitely help in 
integrating them into FPC 1.0.x RTL. I have a slight problem with the 
new files, though - I probably wouldn't like to commit them to the 
FPC RTL with those {$IFNDEF FPC} and {IFDEF OVERLOADSUPPORTED}, etc. 
directives. Do you think it can be solved somehow? Or should I take 
it it's just a temporary solution until you have everything moved 
from SPCC to FPC and these will only be modified for FPC only and 
committed to the FPC CVS tree afterwards?
 Regarding SysSibyl contents - if you only need this initialization, 
then we could probably integrate it in the System unit. The get 
thread ID routine should either go to the new prt0.as for the native 
OS/2 RTL target (and be rewritten to AT&T assembly and directly use 
FS: instead of the DB helper; probably preferred solution), or use 
the appropriate OS/2 API call to remove FS contents dependance (it 
doesn't matter within the prt0 loader, but I'd prefer to avoid it in 
Pascal code).
 I'm not sure what you plan to do with "USE_LIBC" conditional 
(rtlconfig.inc), but we (FPC team) have agreed to not use libc in FPC 
RTL for whatever target (the universal POSIX target for otherwise 
unsupported Unix platforms might be the only exception to this). You 
can achieve smaller binary sizes by creating our own DLL with FPC RTL 
once DLL creating is ready for FPC.

Tomas

-----------
To unsubscribe yourself from this list, send the following message
to [EMAIL PROTECTED]

     unsubscribe sibyl
     end

Reply via email to