{"id":29,"date":"2009-07-30T08:41:30","date_gmt":"2009-07-30T15:41:30","guid":{"rendered":"http:\/\/www.imaginarybillboards.com\/?p=29"},"modified":"2009-07-30T08:41:30","modified_gmt":"2009-07-30T15:41:30","slug":"passing-parameters-by-name-with-perl-plus-easier-emailing","status":"publish","type":"post","link":"http:\/\/www.imaginarybillboards.com\/?p=29","title":{"rendered":"Passing parameters by name with perl, plus easier emailing."},"content":{"rendered":"

One of the advantages of python et al is that instead of taking parameters in order, you can pass them by name. \u00c2\u00a0In python, this is done using (by convention) the following notation:
\n
\ndef myfunction(self,*args,**kwargs):<\/code><\/p>\n


\nparam1 = kwargs['param1']
\nparam2 = kwargs['param2']<\/code><\/p>\n


\netc...
\nmything=myfunction(param1=something, param2=something2)<\/code><\/p>\n


\n<\/code>
\nI can do the same thing in perl with just a tiny bit of extra work. – This is how I actually usually send emails in a program, for example.<\/p>\n

package include;
\nuse MIME::Lite;
\nsub send_email()
\n{<\/code><\/p>\n


\nmy $ref = shift || return;
\nmy %pass = %$ref; #this converts it to a hash - broken out for clarity
\n#from here out, we can just:
\nmy $subj=$pass{'subject'};
\nmy $body=$pass{'body'};
\nmy $file=$pass{'file'};
\nmy $to =$pass{'to'};
\nmy $from=$pass{'from'};
\nmy $debug = $pass{'debug'} || 0;<\/code><\/p>\n

my $msg=MIME::Lite->new(<\/code><\/p>\n


\nTo => $to,
\nFrom => $from,
\nSubject => $subj,
\nType => 'multipart\/mixed'<\/code><\/p>\n


\n) or die (\"Couldn't create multipart email: $!\\n\");
\n$msg->attach(<\/code><\/p>\n


\nType => 'TEXT',
\nData => $body<\/code><\/p>\n


\n) or die(\"Couldn't attach the text part: $!\\n\");
\nmy @filelist=();
\n@filelist=split(\",\",$file) if $file;
\nforeach my $filename(@filelist)
\n{<\/code><\/p>\n


\nprint \"Attaching file $filename\\n\" if $debug;
\nmy $suffix=( split(\/\\.\/,$filename) )[-1];
\nif($suffix eq 'png' or $suffix eq 'jpg' or $suffix eq 'gif' or $suffix eq 'jpeg')
\n{$suffix=\"image\/$suffix\";}
\nelse
\n{
\n$suffix=\"appliation\/$suffix\";
\n}
\n$msg->attach(<\/code><\/p>\n


\nType => $suffix,
\nPath => $filename,
\nFilename=> $filename,
\nDisposition=>'attachment'<\/code><\/p>\n


\n) or die(\"Couldn't attach file attachment: $!\\n\");<\/code><\/p>\n


\n}
\nMIME::Lite->send('smtp','smtp_hostname')
\n$msg->send<\/code><\/p>\n


\nor die(\"Couldn't send message: $!\\n\");<\/code><\/p>\n


\n}<\/code><\/p>\n

#usage:
\n&include::send_email({<\/code><\/p>\n


\nsubject =>\"My email\",
\nto =>$mailto,
\nfrom =>'someone@somewhere',
\nbody => $msg_body,
\nfile => join(\",\",@attachments),<\/code><\/p>\n


\n});
\n<\/code>
\nSo, this is in my include module (as seen in the usage) that other programs import. From then on it’s just a matter of a few lines to send emails, and no remembering the position of the arguments either. This is very similar to how I like to pass paramters to a program using CGI.<\/p>\n

The other nice part of this is it’s guaranteed. \u00c2\u00a0No importing another module, having to use an object, etc.<\/p>\n","protected":false},"excerpt":{"rendered":"

One of the advantages of python et al is that instead of taking parameters in order, you can pass them by name. \u00c2\u00a0In python, this is done using (by convention) the following notation: def myfunction(self,*args,**kwargs): param1 = kwargs[‘param1’] param2 = kwargs[‘param2’] etc… mything=myfunction(param1=something, param2=something2) I can do the same thing in perl with just a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[15],"tags":[10],"_links":{"self":[{"href":"http:\/\/www.imaginarybillboards.com\/index.php?rest_route=\/wp\/v2\/posts\/29"}],"collection":[{"href":"http:\/\/www.imaginarybillboards.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.imaginarybillboards.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.imaginarybillboards.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.imaginarybillboards.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=29"}],"version-history":[{"count":12,"href":"http:\/\/www.imaginarybillboards.com\/index.php?rest_route=\/wp\/v2\/posts\/29\/revisions"}],"predecessor-version":[{"id":41,"href":"http:\/\/www.imaginarybillboards.com\/index.php?rest_route=\/wp\/v2\/posts\/29\/revisions\/41"}],"wp:attachment":[{"href":"http:\/\/www.imaginarybillboards.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=29"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.imaginarybillboards.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=29"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.imaginarybillboards.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=29"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}