Re^2: Multi-threading ping of a list of hosts.....Again!

Oh, no,....it did work then, Honestly Abigail. Well the pinging of mass host names did work with this script. But what didn't work was when I tried to adapt it so that it gathers share and folders sizes simultaneously. But then I got help from BrowserUk and by using WSH and multithreading the problem was solved.

Sorry, I am a bit slow learner.

I have spoken to Damian Conway in person 2 weeks ago – during his Aikido presentation - and having explained my trials and tribulations with Multithreading (I can hear most of you would saying 'trial and tribulation in everything Blackadder :-D' he informed that him and Larry Wall are working on Perl version 6 which will address most of short falls of multithreading in Perl. I asked about the reentry into Win32::OLE hash when multithreading and he informed that this will also be addressed. That’s all the information I managed to get from Damian. ...Just thought I share this with you,…..BTW: Congratulation to Larry Wall for his daughters wedding and I wish him well and speedy recovery.

Blackadder

Comment on Re^2: Multi-threading ping of a list of hosts.....Again!

Replies are listed 'Best First'.
Re^3: Multi-threading ping of a list of hosts.....Again! by blackadder (Hermit) on Sep 20, 2004 at 16:42 UTC
Sorry (again),...I thouht the above post was from Abigale. Cheers Blackadder	[reply]
Re^3: Multi-threading ping of a list of hosts.....Again! by BrowserUk (Patriarch) on Sep 20, 2004 at 21:29 UTC
Sorry, I am a bit slow learner. A pre-requisite for learning, is attempting. Had you at least attempted to adapt one of the previous answers working code to your problem and then come back for help, it would have seemed less like you were asking for a canned solution. Perl version 6 which will address most of short falls of multithreading in Perl. Two problems: P6 is still at least a year away, as it has been for the past two (and more) years. I too once believed that P6 would be the saving grace of threaded Perl. Unfortunately, it appears that it's threading model will be firmly based on the same terminally broken underlying model (pthreads) as both p5 implementations. It also appears to me, as an interested, somewhat knowledgable but otherwise impotent external observer, that at least 1/2 of the design team of Parrot have an active agenda to ignore the requirements (and with it, the benefits) of the threading model of multitasking. I could be misreading the signs, and things could change, but I have given up my hopes of P6 being a truely cross-platform multi-tasking capable language. Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "Think for yourself!" - Abigail "Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon	[reply]