<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Lucida Handwriting";
panose-1:3 1 1 1 1 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="Section1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">I agree with Mark in that I found John's technical review to be excellent. I did get a sense of tone, it would have better without the color comment in emails,
and it took me awhile to get past that tone to review the rest of his comments honestly. I do see the color in my email.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">As always, we would all probably have written this differently, as Andrew stated, but John was bringing home a point that is typically a pet peeve of mine,
code duplication, which in this case was kind of minor, but is all too often seen at much larger scales.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">BTW, I do not know anyone other than I have met Andrew and have nothing but respect for what he has done for this group for years. We are seeing a lot of
"tone", in these few messages, and the scary part is that we all too often cannot read the actual "tone" in email.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Lucida Handwriting";
color:blue"><a href="http://pww.directory.healthcare.philips.com/empl.asp?id=xADOxkTMwADM">Rick Croote</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Software Development Engineer
</span><span style="font-size:
11.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Philips Healthcare - Ultrasound R&D<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Work: 425.487.7834 Mobile: 425.346.6246<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">E-mail:
<a href="mailto:jeff.rahm@philips.com">rick.croote@philips.com</a><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> spug-list-bounces+rick.croote=philips.com@pm.org [mailto:spug-list-bounces+rick.croote=philips.com@pm.org]
<b>On Behalf Of </b>Mark Mertel<br>
<b>Sent:</b> 2009 Feb 25 9:21 AM<br>
<b>To:</b> Andrew Sweger<br>
<b>Cc:</b> spug-list@mail.pm.org<br>
<b>Subject:</b> Re: SPUG: Regexp::Assemble question<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma","sans-serif"">Mr. Sweger,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma","sans-serif"">I'm no expert, but it seems to me that Mr. Krahn's comments are all perfectly valid, and I can detect no ill intent, or slander towards the original poster. His are the types of comments to
be expected during a professional code review. Were these directed at code I had written, I would welcome them rather than take them personally.<br>
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Tahoma","sans-serif"">---<br>
Mark Mertel<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<hr size="1" width="100%" align="center">
</span></div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Andrew Sweger <andrew@sweger.net><br>
<b>To:</b> John W. Krahn <jwkrahn@shaw.ca><br>
<b>Cc:</b> SPUG <spug-list@mail.pm.org><br>
<b>Sent:</b> Wednesday, February 25, 2009 8:55:13 AM<br>
<b>Subject:</b> Re: SPUG: Regexp::Assemble question<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
On Tue, 24 Feb 2009, John W. Krahn wrote:<br>
<br>
> Emails do not have colours, they are just plain text.<br>
<br>
Mine doesn't. But I know some do. Regardless, Amit's intent was still<br>
understood. <br>
<br>
> Is this your actual code? If so, you don't need the subroutines at all, <br>
> you just need the keys. And why use a hash reference instead of a hash?<br>
<br>
Your tone suggests that all Perl programmers should use it in the same way<br>
(your's aparently). Where I come from, Perl is spoken by people of every<br>
skill level; from baby-perl-talk to uber-l33t-golpher-perl. If the code<br>
works, it works. Style and convention mostly become a matter of teamwork.<br>
This list is about learning and sharing Perl. I suspect you might not have<br>
realized this (considering your reply to Amit and your previous reply to<br>
this list).<br>
<br>
> Why all the duplicate code?<br>
> <br>
> my $mode = qx(file $filename) =~ /gzip/i ? '<:gzip' : '<';<br>
> open MYINPUTFILE, $mode, $filename or $Logger->logdie( "Error <br>
> opening file: $!" );<br>
<br>
Again, TIMTOWTDI.<br>
<br>
> No need for this variable as Perl provides the $. built-in variable that <br>
> keeps track of the current line number.<br>
<br>
Maybe so, but $lines is a lot more obvious than $. when it comes time to<br>
review or update the code. Perhaps $INPUT_LINE_NUMBER (via <a href="http://english.pm/" target="_blank">
English.pm</a>)<br>
could be even more obvious (and mean *exactly* the same thing as $.,<br>
whereas $lines could actually mean something slightly different!).<br>
<br>
> Those people who think they know everything are a great<br>
> annoyance to those of us who do. -- Isaac Asimov<br>
<br>
Wow. Again?<br>
<br>
Let me put it simply: knock it off. If you want to bash people about how<br>
they write Perl, go hang out on Usenet or some obscure IRC channel. It's<br>
not welcome here.<br>
<br>
-- <br>
Andrew B. Sweger -- The great thing about multitasking is that several<br>
things can go wrong at once.<br>
<br>
<br>
<br>
<br>
<br>
_____________________________________________________________<br>
Seattle Perl Users Group Mailing List<br>
POST TO: <a href="mailto:spug-list@pm.org">spug-list@pm.org</a><br>
SUBSCRIPTION: http://mail.pm.org/mailman/listinfo/spug-list<br>
MEETINGS: 3rd Tuesdays<br>
WEB PAGE: http://seattleperl.org/<o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1">The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified
that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.<br>
</font>
</body>
</html>