[fpc-pascal]Synapse for FPC

[Marco van de Voort]

> On Tue, 22 Jul 2003, Marco van de Voort wrote:
> 
> > > Today I release new version of my 'Ararat Synapse'. (rel. 32)
> > >
> > > What it is?
> > > 'Ararat Synapse' is TCP/IP library for Delphi, C++Builder and Kylix.
> > > Now it is for FreePascal too! It can be used for Wn32 systems and for
> > > Linux systems too.
> > >
> > > Synapse is set of non-visual classes and procedures for TCP/IP
> > > programming. (IPv4 and IPv6 protocols is supported).
> > >
> > > Additionally you can use my implementations of SMTP, POP3, IMAP4,
> > > SNMP, NTP, SNTP, DNS, Syslog, FTP, TFTP, HTTP or LDAP protocols. You
> > > can also use my MIME encoding and decoding engine, you can use my
> > > charset transcoding engine... and lot of more stuffs. ;-)
> > >
> > > For more informations look to 'Ararat Synapse' web.
> >
> > I looked at the unit (mainly the synsock unit), and I see a Delphi project
> > patched for Kylix, which is patched for FPC/Linux.
> >
> > If you want to make it more generic (I think Solaris/*BSD/MacOSX should be
> > possible long term), you need to clean up some things:
> >
> > - Make a global include file, that stores things like FPC mode, and
> > 	all the defines set in each unit.
> > - Move OS dependant things for a unit as synsock to include files or units.
> > - Separate everything under $IFDEF LINUX in real Linux stuff (like kernel
> > 	structures, glibc base and derived types), and "unix" generic stuff.
> > - Try to get as many of these structures etc from generic units as Linux/Unix
> >       sockets etc.
> 
> As far as I was told, this is explicitly not done, so an alternate TCP/IP
> implementation can be dynamically loaded.

Why would an alternate implementation be unloadable just because the built-in
default one uses a few units?

Libc and Windows are also statically loaded, and I don't see any difference
with the other units.