Re: What does *{"$callpkg\::$_"} = \&{"$pkg\::$_"} mean and how do I fix it?

On Jun 30, 2005, at 4:21, Siegfried Heintze wrote: I have the following line of code: my $id = async { &PopulateIndustryCompanyJobs($sIndustryName, $nThread); $qCompleted->enqueue($sIndustryName); } It causes this error: Prototype mismatch: sub main::async (&;@) vs (&) at c:/Perl/lib/ E

fork() and returning hash / strings to the parent

Hi all, I have some subroutines that return information. Since the each subroutine takes a snapshot of data on networked servers that should be compared, I want the subroutines to execute in the shortest time possible - I'd like to get all the subroutines running at the same time. I thought of u

fork() and returning hash / strings to the parent - take2

// Apologies for the wonderful Oulook formatting in the last email. I'm posting again so everyone can read it. Hi all, I have some subroutines that return information. Since the each subroutine takes a snapshot of data on networked servers that should be compared, I want the subroutines to execu

Re: What does *{"$callpkg\::$_"} = \&{"$pkg\::$_"} mean and how do I fix it?

[Sent a few hours ago, but apparently lost somewhere. I resent it just in case.] On Jun 30, 2005, at 4:21, Siegfried Heintze wrote: I have the following line of code: my $id = async { &PopulateIndustryCompanyJobs($sIndustryName, $nThread); $qCompleted->enqueue($sIndustryName); } It cau

Why XML not well formed?

Hi all, I encountered a really weird error while using perl script to search in a big XML/RDF file (225MB) in CGI. I don't know what's wrong with it as the script works perfectly with a sample XML/RDF file (only 4K) which has the same format as the big one and their only difference is the fi

usage of do {}

Hello everyone, Here and there on the web I encounter claims that the do {} operator is depreciated. However I find it convenient to do things like: eval { some stuff } or do { some multiline error handling }; is this a bad practice? Thanks Peter -- To unsubscribe, e-mail: [EMAIL PROTECTED

Re: date range....

On 6/29/05, Chris Devers <[EMAIL PROTECTED]> wrote: > On Wed, 29 Jun 2005 [EMAIL PROTECTED] wrote: > > > what is lwp? > > Try Google. > > > > Most or all of the top 20 hits are related to Perl's LWP. > > Search for 'lwp perl' and nearly all the top 50 h

xml::simple, $hash ?

Hi all I have a hash that I am trying to populate for XML::Simple $fullXmlHash{$agentBookingSearch."BookRef_".$xmlData{'bookref'}} = \%xmlData; This work perfectly and I get the info as so 17:20:58 etc 100122 13:37:07 B ZAR etc But now I

Re: usage of do {}

On 6/30/05, Peter Rabbitson <[EMAIL PROTECTED]> wrote: > Here and there on the web I encounter claims that the do {} operator is > depreciated. However I find it convenient to do things like: > > eval { some stuff } or do { some multiline error handling }; > > is this a bad practice? No, that's

Re: fork() and returning hash / strings to the parent

zentara wrote: > On Thu, 30 Jun 2005 10:32:07 +0200, [EMAIL PROTECTED] (Tielman > Koekemoer \) wrote: > >>I have some subroutines that return information. Since the each >>subroutine takes a snapshot of data on networked servers that should >>be compared, I want the subroutines to execute in the s

Re: xml::simple, $hash ?

Brent Clark wrote: > Hi all > > I have a hash that I am trying to populate for XML::Simple > > $fullXmlHash{$agentBookingSearch."BookRef_".$xmlData{'bookref'}} = > \%xmlData; > > This work perfectly and I get the info as so > > > > 17:20:58 > etc > 100122 > > > 13:

Re: usage of do {}

Peter Rabbitson wrote: > Hello everyone, > Here and there on the web I encounter claims that the do {} operator is > depreciated. However I find it convenient to do things like: > > eval { some stuff } or do { some multiline error handling }; > > is this a bad practice? > > Thanks > > Peter >

Re: usage of do {}

On 6/30/05, Wiggins d'Anconia <[EMAIL PROTECTED]> wrote: > Peter Rabbitson wrote: > > Hello everyone, > > Here and there on the web I encounter claims that the do {} operator is > > depreciated. However I find it convenient to do things like: > > > > eval { some stuff } or do { some multiline error

Use of uninitialized value... --> quit!

Often when debugging my scripts I get: Use of uninitialized value in print at line 52. Use of uninitialized value in print at line 52. Use of uninitialized value in print at line 52. Use of uninitialized value in print at line 52. Use of uninitialized value in print at line 52. Use of uninitiali

Re: Use of uninitialized value... --> quit!

Bryan R Harris wrote: > > Often when debugging my scripts I get: > > Use of uninitialized value in print at line 52. > Use of uninitialized value in print at line 52. > Use of uninitialized value in print at line 52. > Use of uninitialized value in print at line 52. > Use of uninitialized value i

Re: usage of do {}

On 6/30/05, Jay Savage <[EMAIL PROTECTED]> wrote: > Checking for $@, though, is a must no matter what you're using [eval] for. +1 despite my completely missing that omission earlier! -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: usage of do {}

On Thu, Jun 30, 2005 at 09:05:00AM -0600, Wiggins d'Anconia wrote: > Peter Rabbitson wrote: > > Hello everyone, > > Here and there on the web I encounter claims that the do {} operator is > > depreciated. However I find it convenient to do things like: > > > > eval { some stuff } or do { some mu

Re: usage of do {}

Peter Rabbitson wrote: > On Thu, Jun 30, 2005 at 09:05:00AM -0600, Wiggins d'Anconia wrote: > [snip previous round] > > I am sorry, I wasn't clear enough. I am aware of eval returning the last > statements return value, thus the possibility of having an undef result. > I am using it exclusive

Re: usage of do {}

Wiggins d'Anconia wrote: > Peter Rabbitson wrote: > [snip] > > Either way there shouldn't be a need for eval unless you have raise > error on, but in that case you should catch the exception with [EMAIL > PROTECTED] > > http://danconia.org > > >>Thanks for the feedback >> >>Peter >> > > Ju

Re: usage of do {}

> Just as a side note... this is really a stylistic or idiomatic argument. Precisely right. That once again is a bad example I guess :) It is just dictated by the way all the rest of the error handling is done. For example: sub check_table { my ($dbh, $table) = @_; $table = lc $table;

Re: Use of uninitialized value... --> quit!

> Bryan R Harris wrote: >> >> Often when debugging my scripts I get: >> >> Use of uninitialized value in print at line 52. >> Use of uninitialized value in print at line 52. >> Use of uninitialized value in print at line 52. >> ... >> >> -- filling up my terminal window. Is there any way to t

Re: Use of uninitialized value... --> quit!

Bryan R Harris wrote: > >>Bryan R Harris wrote: >> >>>Often when debugging my scripts I get: >>> >>>Use of uninitialized value in print at line 52. >>>Use of uninitialized value in print at line 52. >>>Use of uninitialized value in print at line 52. >>>... >>> >>>-- filling up my terminal window.

Re: Use of uninitialized value... --> quit!

> Bryan R Harris wrote: >> >>> Bryan R Harris wrote: >>> Often when debugging my scripts I get: Use of uninitialized value in print at line 52. Use of uninitialized value in print at line 52. Use of uninitialized value in print at line 52. ... -- filling

Perl training material required.

Hi All, Can anyone provide me the site which have good teaching material for perl. I need to give training on perl basics and I don't have time to prepare the material. Thanks in advance. -Original Message- From: feanor To: beginners@perl.org Sent: 6/24/05 12:21 PM Subject: Perl mod

Interactive with other program

hi, I want to write a perl script that interactive with other program or script. when I run the jacl script which askes me to input some parameters interactively, just like this, when I issue java -jar install.jar , then I have to answer some questions like below, enable security ? (true|false)