| Zaphar_home | nope |
| integral | Sheesh, serious lack of brain cells. |
| Zaphar_home | doesn't work if I uncapitalize says I can't call method BUILDALL on an ublessed reference dazjorz: this isn't as simple as you can get to using moose what am I missing? |
| somian | Hah Hah |
| desudation | tag: What you are saying seems to be at least partially at odds with http://perl.apache.org/docs/2.0/user/coding/coding.html#Threads_Coding_Issues_Under_mod_perl |
| shorten | desudation's url is at http://xrl.us/vcfs |
| pasteling | "fud" at 84.72.32.18 pasted "poo" (1 line, 67B) at http://sial.org/pbot/23514 |
| desudation | tag: (sorry dropped). My question is whether a call like readdir made from two threads concurrently is capable of corrupting the stack or leading to segmentation fault. Specifically on Windows. |
| dazjorz | Zaphar_home: I don't know about "has attrib" I don't know about "Moose" either |
| fud | tag: that sounds like an easy thing to test |
| Zaphar_home | well you guys are no help at all :-) and google has nothing on this either |
| tag | desudation: Are you familiar with how threads work? desudation: Assumptions that are safe to make: If the two operations will not be reading or writing to a shared data structure, a mutex lock is not required for their operation |
| fud | insofrar as they should be used with reckless abandom |
| tag | desudation: If two threads could potentially read from the same data structure, access to this data must be synchronized. |
| dazjorz | Zaphar_home: well, only think I could say is check Moose's source omg, he already left. -_- |
| milky_cereal | hi Caelum. we talked yesterday about perl/tk. i'm now going with this. is perltray from activestate the only reliable way of making a tray icon with perl? i see some scripts out there, but they don't seem reliable. For instance, there's one on perlmonks that shows up early on google, but the comments indicate it doesn't work. |
| dazjorz | ass |
| tag | desudation: in perl, data that is not *shared* may not be accessed from an individual thread, thus, all calls are safe until the datastructures they use are marked shared desudation: additionally, why are you using perl for multithreadding? (or are you?) desudation: additionally, why are you using perl for multithreadding? (or are you?) desudation: don't know if you saw my other response also why are you using CGI:IRC ? :-)( |
| solemnwarning | Can I use $buf+$write to access $buf, $write bytes in like in C? |
| desudation | tag: Thinking about it, perhaps I haven't explained myself well. The threads are actually running on different interpreters in the same process space. They aren't sharing data structures at all. |
| solemnwarning | Actually, how can I remove the |
| tag | solemnwarning: come again that question doesn't make sense |
| solemnwarning | Actually, how can I remove the first $x bytes from $var? |
| tag | desudation: ithreads. desudation: then you have no concerns |
| solemnwarning | $var is a string |
| milky_cereal | is there any way to make a tray icon with perl besides perltray from activestate? |
| tag | until you *use* threads::shared for something and share a datastructure |