in reply to Re: Keeping an INET socket inside a shared object
in thread Keeping an INET socket inside a shared object

Again, I am getting the feeling I am trying to bend the language for something it was not supposed to perform... :oO

No. You are simply trying to achieve your goal using techniques more suited to other languages.

Eg. In C, it is quite normal to process files one character at a time using something like this:

while ((c = getchar()) != EOF){ ... }

That is quite efficient in C; but doing the same thing in Perl (using getc()) is horribly inefficient; so you never see it done that way.

You appear to be wanting to use javaesque programming techniques in Perl; and then complain because they don't work the same way.

If you work with Perl and iThreads they can be very simple, efficient and effective. Work against them and you'll go away complaining that the tool is faulty ....


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.