[Phoenix-pm] Perl threads?

[Brock]

That would be sweet.

While we're on the topic:

$/='}"6ft.(&^)+@<B#,/JK2=>?@7$eJp.',$"
=eval$/,@/=split//,$/.$@,$/=0;while($/
<26){$_.=$/[ord($/[++$/])-7]}print

Does everyone know the JAPH game?
--Brock

On 2006.01.26.12.16, Michael Friedman wrote:
| So, assuming the examples are regular perl inside the POD, does the  
| book manuscript compile and run? And is the final output "Just  
| Another Perl Hacker"? :-)
| 
| -- Mike
| 
| On Jan 26, 2006, at 12:19 PM, Scott Walters wrote:
| 
| > Erm, yes, perldoc, by special request. I actually wrote it in perldoc
| > format and wrote a script to convert it to RTF. Me: "Do I *have* to
| > use Microsoft Word?" APress: "Yes" (half way through the process)
| > Me: "Surprise! I'm not using Microsoft Word!" APress: "Uh, okay, that
| > would explain why bullet lists look funny" Me: "Yeah, I'm not sure
| > what's up with that..."
| >
| > -scott
| >
| > On  0, Bill Nash <billn at odyssey.billn.net> wrote:
| >>
| >> On Thu, 26 Jan 2006, Scott Walters wrote:
| >>
| >>>
| >>> P.S.: check out forks.pm -- it's an implemention of the thread API,
| >>> so Thread::Queue etc all work, but build on top of fork and IPC.
| >>> If you need threads because of CPU bound tasks but there isn't
| >>> too much variable sharing and locking, I'd go this route.
| >>
| >> Thanks for the pointer, doing some light reading now.
| >>
| >>> P.P.S.:
| >>>
| >>> Buy my damned book, damnit.
| >>
| >> Does it come in man page or perldoc form? =D
| >>
| >> - billn