RE (tilly) 2: Just enough to be dangerous (on threads) indeed! :-)

Ack! I knew that as well. It is just that fork() is so much a Unix idea that I think of it as "the Unix way" even though Unix also has many other ways of working.

Incidentally on machins that support it, you can use shared memory from Perl with IPC::Shareable.

Comment on RE (tilly) 2: Just enough to be dangerous (on threads) indeed! :-)

Replies are listed 'Best First'.
RE: RE (tilly) 2: Just enough to be dangerous (on threads) indeed! :-) by lhoward (Vicar) on Aug 25, 2000 at 22:59 UTC
I find IPC::Shareable extermely handy. Very frequently I want programs to be able to exchange some pieces amounts of data; and I want them to do it quickly. Files are too slow and "real" TCP/IP networking can be a hastle for just sharing a little data. Also when the processes aren't related (i.e. they wouldn't fork to create each other under the processes model ; they wouldn't be separate threads under the therading model) it is just really handy to use IPC::Shareable. Its just that so many people think its either "pipes or TCP/IP" when their processes need to communicate. SysV IPC is extremely apropriate for some problems.	[reply]

Replies are listed 'Best First'.

RE: RE (tilly) 2: Just enough to be dangerous (on threads) indeed! :-)
by lhoward (Vicar) on Aug 25, 2000 at 22:59 UTC

IPC::Shareable

Its just that so many people think its either "pipes or TCP/IP" when their processes need to communicate. SysV IPC is extremely apropriate for some problems.

[reply]