background: i have to deal with a lot of configuration variables for paths and URIs. these being entered by humans, there is no guarantee that the path|uri does or does not end with a slash.

solution? for files, this is easy; use File::Spec:
use File::Spec; my $filepath = File::Spec->catfile( $dir, $filename );
but what about URIs? i don't see any handy methods on the URI class for appending values. so i had an idea, i could use File::Spec::Unix to manipulate the path portion of the URI.
use File::Spec::Unix; use URI; my $uri = URI->new( $base ); $uri->path( File::Spec::Unix->catfile( $uri->path, 'foo.html' ) );
my question is, is this a good idea or bad idea? am i overlooking an existing best/common practice for dealing with this?

In reply to URI plus File::Spec::Unix -- good idea or bad? by mreece

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.