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/
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
// 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
[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
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
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
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 not bad
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 shortest
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
?xml version=1.0 standalone=yes
opt
ebkBookRef_100122
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
Didn't
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 handling };
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
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 in print
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]
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 multiline
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 exclusively
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
Just as a side
Just as a side note... this is really a stylistic or idiomatic argument.
snip
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
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 tell perl to 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. Is there any way to tell
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. Is there any
21 matches
Mail list logo
