RE: Beta Testing a Robot

[Shaw, Matthew]

My $0.02 on this:

While it may be a worthwhile personal pursuit to write a script that
provides relevant results from google based on the text of someone's
email/news posting/etc, I don't think this is the forum for it. These
are very busy lists to start with and this essentially will result in
doubling the 'new' traffic to the list with information that is
irrelevant to anyone but the original poster. The irrelevancy of the
auto responder will increase when faced with questions by folks that are
so far off that they're not even asking the right question to begin
with(seems to be somewhat common in these groups). For these people,
investigative questioning is the only correct response and an
autoresponder (with a lot of text - read: information overload) will
only confuse them more.

 If anything, the response should go directly to the poster, not to the
list. IE: 

Your question has been posted to the XXX List, while you're waiting for
someone to respond, try out these links from google.com that may or may
not be relevant to your query:

1. link Google Desc
...
10. link Google Desc

Also, googling should be the first resort of any technical person. I
think the list FAQs should be updated in Section 2, Question 9 'Other
Tips Before Posting To The List' with something like:

_1._ Try to google.com with your question first! Google has extremely
relevant search results and may preclude asking your question to the
list. 

Tossing his copper in the pot,
Matt Shaw
Technical Architect
xwave, An Aliant Company
Bus: 506-389-4641 (Mctn)
Bus: 506-444-9639 (Fred)
Cel: 506-863-8949
[EMAIL PROTECTED]


 -Original Message-
 From: Casey West [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, December 03, 2003 3:41 PM
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: Beta Testing a Robot
 
 
 I'm beta-testing a robot that searches Google when new 
 questions are posed to the beginners' lists.  I have no idea 
 if it will be useful.
 :-)
 
 I'm going to watch it closely and hope it is.  I'll remove it 
 if I find that it does a bad job.
 
   Casey West
 
 -- 
 Good Idea: Kissing a loved one.
 Bad Idea:  Kissing a total stranger. 
 
 
 -- 
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Formatting integer input: use the sprintf() in perlfunc - Perl builtin functions

[Shaw, Matthew]

 whenever you need to do any special formatting like this, 
 especially numbers, use the sprintf() in  perlfunc - Perl 
 builtin functions for your case, try this:
 
 print sprintf(%05.02f\n, 4.5 );
 04.50

Why not just use 'printf()' for this? Makes it somewhat less confusing
while doing essentially the same thing in the background:

printf %05.02f\n, 4.5;

The difference lies in if the '$\' ($OUTPUT_RECORD_SEPERATOR) is set
when you use the first example it will add an extra newline that you
probably would not intend (given the \n in the format). printf() will
ignore the value of $\ and format only according to your format
argument.

Just a suggestion.

Matt



 
 -Original Message-
 From: Sara [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, August 20, 2003 1:21 PM
 To: beginperl
 Subject: Formatting integer input
 
 
 $one = 2.5;
 $two = 2;
 $three = $one + $two;
 
 print $three; # prints 4.5
 
 I want 4.5 in proper format as 04.05
 
 Any ideas?
 
 Thanks,
 Sara.
 
 
 
 -- 
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]