Greeting Monks,
I need to parse data like this: .command parameter
Here is what I got so far: 
#!/usr/bin/perl
#get command portion of data
use strict;

my ($stripped,$cmd,$cmd_loc,$cmd_locend);
    
$stripped = ".command parameter";
$cmd_loc=index($stripped,".");
$cmd_locend=index($stripped,chr(32));
$cmd=substr($stripped,$cmd_loc,$cmd_locend++);

print $cmd."\n";

[download]
This works just fine, but when I try to check if there is no parameter (I know it has to do with the chr(32), since there would be no space if it was only a command :P), but all the attempts to check for this have failed. I've tried checking to see it $cmd_locend == -1, etc.

I know this is a simple problem, but I guess I've been looking at the code to long, and have lost sight of it :\. Any help will be greatly appreciated!
Thanks
^jasper <jasper@wintermarket.org>

Title edit by tye

In reply to Parsing small string by Jaspersan

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.