> And the other way around. The main problem with Borland is that it only > supports one and a half platform on one processor.
Sure, but Borland is home for Synapse. I create Synapse primary for my programs. I am professional programmer and I create lot of commercial programs by my Synapse. This is reason why Borland is very important for me. Programming is not only compiler, but IDE too! I not see comparable IDE for FPC with Borlands IDE. ;-( FPC is only new playground for me now. Until FPC have comparable GUI based IDE with Borland's IDE, then I cannot use FPC for hard developing. ;-( FPC is new world for me. I do only first step to this world! yes, Synapse is not support lot of other platforms, but why? Because I am on begin of the way. > Don't take it personally. It is meant as constructive criticism for the long > run. However if you are aware of the issues it is easier to work in the > direction Ok. For discussing about internals in Synapse you can use special email list called Synalist. :-) > > this is step back in features of Synapse. In old times it is used by this > > way. However now Synapse can use ANY socket library by dynamic loading. > How? How do I load FPC sockets unit, and avoid compiling in the non working > Linux kernel structuers in e.g. BSD? I not mean pascal library, i mean system library. Under Win32 you can load any DLL with same interface as winsock. Under Linux you can load any '.so' file with same socket interface as libc. This is very important for me, because I need this in my some special commercial programs. Of course, whn I go to platform without dynamic loading libraries, then I still can map my synsock to any static socket library. It is not a problem. _______________________________________________ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal
