|The stupid question is the question not asked|
Re: Socket client thread design problemby BrowserUk (Pope)
|on Mar 20, 2014 at 15:45 UTC||Need Help??|
So any advise on realizing this behavior without running into all this trouble created by the differences in the threading model of C and Perl?
Advise: stop trying to emulate the C code. There are many programming techniques used in C that are either suboptimal or impossible to realise in Perl. There is always a better Perlish solution.
But you have to step back from the C implementation and look at the required functionality, not how that functionality is achieved in C.
If you would describe the program at a higher level I might be able to suggest something. I'm really intrigued by the idea of a C program running user provided callback code.
(From the description so far, it sounds like your trying to implement a multi-server IRC client with Bot logic; but that's just a guess.)
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.