On Wed, 22 May 2002 19:06:58 +0200 (MET DST), Doodle wrote: > >On Tue, 21 May 2002, Yuri Prokushev wrote: > >> >That's the main reason why I thought that I should better port the full >> >sibyl sources (system.pas and others) to FPC than change the FPC sources >> >for Sibyl. >> Rewrite System unit? Why? System units is same (except some nonstandard >> functions). And rewrite system unit not good idea. >I didn't mean rewrite, just do some modifications to be able to compile it >with FPC. This is true for all other units, but not for system unit. System unit is one of most compiler-depended units. So, required not just stupid changing of one syntax construction to another but rewriting lot of things from scratch. I don't want do this work. From other side, system units interface less or more same for both compilers and I don't have big problems with porting of os2api units.
>But it looks like that your way is "more ready" than mine, so let it be.:) >> >> I know about future problems with sibyl applications. Some rework will be >> >> required for migration to OpenSibyl (At least for application wich uses >> >> imports, APIENTRY, CSTRING, C style comments (/*) and some other things). >> >Yep. >> Translate, pls. >I mean I agree. I think CSTRING can be implemented. I have idea, but not time :( After port of pm* units will be finished I try implement CSTRING type. This reduce lot of work in future. >> I prefer do work on this basis: >> 1) use native fpc rtl (system, dos, crt, sysutils) >> 2) use sibyl os2 api (os2def, bse*, pm*) >> 3) use native fcl as base for spcc (classes) >> 4) use spcc as base for svde >> 5) Add to spcc all methods and properities from delphi vcl (this is allow use >delphi apps based on vcl) >> 6) May be add Odin32 API (this is allow use delphi apps based on win32 api) >> >> When 2) will be done, we can contibute os2 api definetion to fpc/2 team. >> >> Of couse, I don't work with fpc sysutils and classes now. But after success >compilation of SVDE on top of fpc I will work with spcc on top of fcl. > >I afraid (based on my previous tries) that porting sysutils and classes >will be / is the main problem of OpenSibyl. Porting OpenSibyl classes and sysutils not big problem, just big work. But usage of fpc sysutils and classes will be a problem. >Btw, to compile SVDE, you will >need SPCC, so you cannot compile it with fpc until SPCC is ported. Of couse. I mean about moving to SPCC on top of FCL. This remove conflicts with various class libs and allow us begin use LCL. >So, are you at 2) now? Which units are ported yet, and which ones remain? Attached.
todo.txt
Description: Binary data
