Michael Van Canneyt wrote:
I meant the SimpleIPC unit from the FCL:
http://lazarus-ccr.sourceforge.net/docs/fcl/simpleipc/index.html
Because I was exploring various unix-domain socket aspects including
mtu, where they're put, how to recover if an inactive one's already
there (e.g. gdb failure) and so on. And in particular I was exploring
naming issues that were being fouled up by things like Mozilla, trying
to find some balance between the name of the project (known at
compilation time) and the name of the executable after this sort of
thing had caused a lot of local hassle.
So I think you've done better having something that is portable and is
coded fairly elegantly, but I don't think that I've gratuitously
reinvented the wheel.
I never meant to imply that; I just hoped that by pointing you to some
existing code, I could stop you from spending time on something which
already exists.
Of course, time spent learning APIs is never wasted :)
I'll certainly take a close look at that if I come back to this problem-
if nothing else to see whether it works in the context of a single
process :-)
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
