{"id":4389,"date":"2013-02-22T09:00:41","date_gmt":"2013-02-22T14:00:41","guid":{"rendered":"https:\/\/blogs.mathworks.com\/pick\/?p=4389"},"modified":"2013-02-21T19:31:11","modified_gmt":"2013-02-22T00:31:11","slug":"coding-challenge-on-input-parsing-result","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/pick\/2013\/02\/22\/coding-challenge-on-input-parsing-result\/","title":{"rendered":"Coding challenge on input parsing – Result"},"content":{"rendered":"
\r\n \r\n

This week, Jiro<\/a> is highlighting a code snippet submitted by Mikko Leppänen.\r\n <\/p>\r\n

In my previous post<\/a>, I posed a coding challenge to come up with an input validation code snippet to work with boundedline<\/tt><\/a> by Kelly<\/a>. The function is a well-written piece of code with flexible input arguments. Here are the different ways you could call the\r\n function:\r\n <\/p>

[hl, hp] = boundedline(x, y, b)\r\n[hl, hp] = boundedline(x, y, b, linespec)\r\n[hl, hp] = boundedline(x1, y1, b1, linespec1, x2, y2, b2, linespec2)\r\n[hl, hp] = boundedline(. . ., 'alpha'<\/span>)\r\n[hl, hp] = boundedline(. . ., ax)\r\n[hl, hp] = boundedline(. . ., 'transparency'<\/span>, trans)\r\n[hl, hp] = boundedline(. . ., 'orientation'<\/span>, orient)\r\n[hl, hp] = boundedline(. . ., 'cmap'<\/span>, cmap)<\/pre>
Here were the ground rules for the challenge:<\/p>\r\n      
\r\n         
    \r\n            
  1. The function should be able to handle all, except the 3rd, calling syntax above. Any number of the optional arguments can\r\n               be passed in.\r\n            <\/li>\r\n            
  2. The input parameters should meet the respective criteria. (see help boundedline)<\/li>\r\n            
  3. All optional inputs should have default values. (see help boundedline)<\/li>\r\n            
  4. You can assume that the parameter-value pair inputs will be called after the other optional inputs.<\/li>\r\n            
  5. After parsing, the parameters should be put into a structure with fields \"x\", \"y\", \"b\", \"linespec\", \"usealpha\", \"hax\", \"trans\",\r\n               \"orient\", \"cmap\".\r\n            <\/li>\r\n            
  6. (Extra credit) Allow for the 3rd calling syntax.<\/li>\r\n         <\/ol>\r\n      <\/div>\r\n      
    Mikko was the only person who rose to the challenge, and it was great! His solution follows the ground rules, and he even did the extra credit!<\/i> I wrote my own as well, but after seeing Mikko's solution, I was able to improve mine. Today I am going to dissect both of\r\n         our codes and explain in detail.\r\n      <\/p>\r\n   <\/introduction>\r\n   
    Contents<\/h3>\r\n   
    \r\n