This relates to the question I asked yesterday at Net::FTP - syntax with username containing / - since it turns out it's a separate yet related issue than what I thought it was, here goes:

The sub-routine I'm still having a problem with is: 

sub ParseURL
{
  my($url)= shift;
  my($protocol, $site, $login, $password);

  $url=~ /^(\w+):\/*([^\/]+)\/(.*)$/; # chunk the URL components
  $protocol= uc($1);        # preserve matches in real variables
  $site= $2;
  $path= $3;

  if ($site=~ /\@/)
  {                # check for the optional login field
    ($login, $site)= split("\@", $site);
    ($login, $password)=    # check for the optional password field
      split(":", $login);

    return($protocol, $site, $login, $password, $path);
  }
  else
  {                # no account information
    return($protocol, $site, "", "", $path);
  }
}

[download]

Basically my ftp username contains a / (XX/yyyy), and XX is getting parsed as the hostname of the ftp site.

As was suggested, I think the fastest way to fix this is to change the item separator in the text file to a comma or something, rather than a /.

The regex I'm having trouble with is: 

$url=~ /^(\w+):\/*([^\/]+)\/(.*)$/;

[download]

The way I'm reading this is: between  /^(\w+) is $protocol, between  \/*([^\/]+) is $site, and  \/(.*)$ is $path.

So, based on the above, if I use a comma separator for the $site portion, the line should look like: 

$url=~ /^(\w+):\/*([^\/]+),(.*)$/;

[download]

and the appropriate line in my text file looks like: ftp://XX/yyyy:password@123.456.789.012,/ However, when I then run the script, I get several "uninitalized value" errors, one for the pattern match ($site=~ /\@/), one for a line trying to use $host, the other for a line trying to use $path.

So, it seems I'm missing something (hopefully) fairly obvious, but I can't seem to figure it out.

Any help appreciated.

Thanks,

Glenn

In reply to replacing text file separators in regex by Anonymous Monk

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.