Your suggestion would limit me to creating uppercase file names and that would be awful.
Or only lowercase. While this seems overly restrictive, at least you don't run into the problem that within your application you seem to have two files which are conceptionally different (such as Makefile and makefile), but end up being the same file on the OS level.

But I see that to completely rule out upper (or lower) case is too restrictive. For example Perl .pm files are usually written in mixed case. Still, for the files I create, I try to stick to lower case letters unless the circumstances really beg for upper/mixed case.

-- 
Ronald Fischer <ynnor@mm.st>

In reply to Re^5: move command by rovf
in thread move command by gem555

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.