If you look closely at your "$_sensor_type =" statement, you will see that you have different kinds of quotes around "I2600". Notice the difference between them and the first quote in your print statement, ". forward leaning and backward leaning " are different than normal straight up ".
I am surprised that this even compiles. Are you using warnings and strict?
Other than that, I see no reason why I2600 shouldn't match the regex, although the /g is completely unnecessary here. I tested "I2600" on my machine and works great with proper quote characters.
UPDATE: this is not the problem, it appears that previous use of string in an inappropriate global match was the issue..oooops. Although I must say that sometimes these non-printing and/or non-standard characters can and DO cause problems... that is not the case here..
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.