Christopher Brown schreef:
I spent some time thinking about Dr. Ruud's reply over the past
several days. Although I mostly share his views, I think that he has
done a disservice to the discussion of the relative merits of
threading and forking . Like most things in technology different
I spent some time thinking about Dr. Ruud's reply over the past several
days. Although I mostly share his views, I think that he has done a
disservice to the discussion of the relative merits of threading and forking
. Like most things in technology different approaches exploits different
On Sat, Nov 01, 2008 at 01:25:17PM +, Ben Morrow wrote:
Quoth [EMAIL PROTECTED] (Nicholas Clark):
$ /home/nclark/Sandpit/588ish/bin/perl -Mthreads -e0
This Perl not built to support threads
Compilation failed in require.
BEGIN failed--compilation aborted.
No, this still doesn't work.
David Cantrell schreef:
eval use threads || exit(0);
Alternatively written as:
exit(0) unless eval use threads;
(just because I wondered how strong the || was in there)
--
Affijn, Ruud
Gewoon is een tijger.
* Chris Dolan [EMAIL PROTECTED] [2008-11-01 22:25]:
On Nov 1, 2008, at 10:39 AM, Dr.Ruud wrote:
I think it was Randal Schwartz who said something like: If the
answer involves threads, then the question was wrong.
Most likely that quote comes from a year when multi-processor
systems were not
Then Randall is wrong
The Perl threading model is perhaps imperfect but the principle of threads is a
part of many modern applications not to mention every modern OS including
Solaris and MS windows xp
Many client/server apps benefit from threading. Parallel processing hugely
benefits from
On Fri, Oct 31, 2008 at 06:16:01PM -0500, Chris Dolan wrote:
Just add a dependency on thread::shared or one of the other threading
libraries. Push your problem up the chain!
No, not threads::shared
$ /home/nclark/Sandpit/588ish/bin/perl -Mthreads::shared -e0
$
threads looks a better idea:
Quoth [EMAIL PROTECTED] (Nicholas Clark):
On Fri, Oct 31, 2008 at 06:16:01PM -0500, Chris Dolan wrote:
Just add a dependency on thread::shared or one of the other threading
libraries. Push your problem up the chain!
No, not threads::shared
$ /home/nclark/Sandpit/588ish/bin/perl
Gabor Szabo schreef:
I guess we can implement everything with fork but I think -
maybe because of my lack of experience in threads - that it will
be better to use them than to fork.
I think it was Randal Schwartz who said something like: If the answer
involves threads, then the question was
* On Sat, Nov 01 2008, Dr.Ruud wrote:
Gabor Szabo schreef:
I guess we can implement everything with fork but I think -
maybe because of my lack of experience in threads - that it will
be better to use them than to fork.
I think it was Randal Schwartz who said something like: If the answer
On Sat, Nov 1, 2008 at 12:50 PM, Jonathan Rockway [EMAIL PROTECTED] wrote:
Anyway, I wouldn't use threads for this, but that doesn't make threading
an unreasonable approach. I would use POE.
+1
I assume that POE::Loop::Wx should integrate into Padre pretty easily, yes?
-- David
On Nov 1, 2008, at 10:39 AM, Dr.Ruud wrote:
Gabor Szabo schreef:
I guess we can implement everything with fork but I think -
maybe because of my lack of experience in threads - that it will
be better to use them than to fork.
I think it was Randal Schwartz who said something like: If the
Hi,
currently I have this code in Build.PL to check if the perl where Padre
is being installed is threaded.
use Config;
if (not $Config{usethreads}) {
warn Padre requires a perl built using threads\n;
exit 0;
}
Is there any way to add this requirement to META.yml?
Gabor
* On Fri, Oct 31 2008, Gabor Szabo wrote:
Hi,
currently I have this code in Build.PL to check if the perl where Padre
is being installed is threaded.
use Config;
if (not $Config{usethreads}) {
warn Padre requires a perl built using threads\n;
exit 0;
}
Probably off topic,
On Fri, Oct 31, 2008 at 4:14 PM, Jonathan Rockway [EMAIL PROTECTED] wrote:
* On Fri, Oct 31 2008, Gabor Szabo wrote:
Hi,
currently I have this code in Build.PL to check if the perl where Padre
is being installed is threaded.
use Config;
if (not $Config{usethreads}) {
warn Padre
Just add a dependency on thread::shared or one of the other threading
libraries. Push your problem up the chain!
Chris
On Oct 31, 2008, at 7:31 AM, Gabor Szabo wrote:
Hi,
currently I have this code in Build.PL to check if the perl where
Padre
is being installed is threaded.
use Config;
16 matches
Mail list logo