Ask Bjørn Hansen writes:
> On 11/24/10 1:23, Nicholas Clark wrote:
>> The symlink tree is built by scripts, isn't it? Are they available?
> So inadvertently we got to test if anyone cared. The answer is no. :-)
I can't say I'm not anyone, but apparently one of very few :( .
-- Johan
jpie...@cpan.org wrote:
I was wondering what the rationale for staking out a top-level namespace to
match
your username on CPAN is?
In the past, I went through the process and put one module into the
global CPAN name space -- Math::TriangularNumbers:
http://backpan.perl.org/authors/id/
On 11/24/10 1:23, Nicholas Clark wrote:
The symlink tree is built by scripts, isn't it? Are they available?
Actually; since earlier this year it's not being built anymore. I
promised to write a note announcing it but haven't gotten around to it.
So inadvertently we got to test if anyone car
On Nov 24, 7:54 am, sebast...@aperghis.net (Sébastien Aperghis-
Tramoni) wrote:
> [...] the thing that
> really annoyed me recently was the lack of advanced debug tools, for example
> to find memory leaks. None of the tools I found or was pointed to worked
> in my case.
Allow me to recommend my ow
The point of threads is shared address space. They are lighweight and fast to
create. It isn't just parallel processing with fork a new process.
Please understand what threading is ntended to provide before you make
recommendations to do something else nstead.
Sent from my BlackBerry® smartphon
Paul LeoNerd Evans wrote:
On Wed, Nov 24, 2010 at 04:54:31PM +0100, Sébastien Aperghis-
Tramoni wrote:
In terms of Perl itself, apart from the reference syntax, the
thing that
really annoyed me recently was the lack of advanced debug tools,
for example
to find memory leaks. None of the tools
"The biggest problem with fork() is communication between the child and
parent. For that, you need Inter-Process Communication (IPC). "
This is why we have threads. In general one has kernel threads and user
threads. The scheduler is aware of the former not the latter therefore blocking
on an
