I have a big directory of data/code that I am reorganizing following these useful guidelines. As a result I will create a lot of subdirectories. I would like to standardize the subdirectory names with a consistent naming convention that would be compatible with any operating system. Which of the following is more 'standard'? Or suggest another. (I am avoiding spaces).

  1. subdirectory_name
  2. subdirectoryName
  3. SubdirectoryName
link|improve this question

feedback

closed as not constructive by grawity, Dave M, Nifle, Sathya Feb 3 at 11:09

This question is not a good fit to our Q&A format. We expect answers to generally involve facts, references, or specific expertise; this question will likely solicit opinion, debate, arguments, polling, or extended discussion. See the FAQ for guidance on how to improve it.

1 Answer

up vote 1 down vote accepted

There is no standard other than the one you decide on. Currently popular operating systems support all these names equally well, and the organization of your files is your own choice.

In terms of compatibility, all three versions are fine, and there is no reason to avoid spaces, either. In fact, when Windows introduced long file name support in 1995 (upper/lower case and spaces supported, with full Unicode support added in 1996), Unix already had the same for over twenty years (Wikipedia lists V6FS from year 1972). To remind, we're currently in year 2012.

(...Unless you are going to use MS-DOS or VMS as your primary OS, in which case this comparison may be interesting.)

link|improve this answer
Do you think all 3 are equally easy to scan when reading a long list of subdirectories? – KE. Feb 1 at 20:33
feedback

Not the answer you're looking for? Browse other questions tagged or ask your own question.