Re^4: move command

What you seem to be missing is while Windows is case-insensitive, it does remember the case of the name. If you create FOO.TXT, it will show up as FOO.TXT in a directory listing. If you create foo.txt, it will show up as foo.txt. Your suggestion would limit me to creating uppercase file names and that would be awful.

You will find that the second file "replaces" the first one

Not quite. The first file will be truncated, but its name will still be FOO.TXT, not foo.txt.

Comment on Re^4: move command Select or Download Code

Replies are listed 'Best First'.
Re^5: move command by rovf (Priest) on Jul 10, 2009 at 11:12 UTC
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>	[reply] [d/l] [select]
Re^6: move command by ikegami (Patriarch) on Jul 10, 2009 at 16:21 UTC
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. at least you don't run into the problem that within your application you seem to have two file names which are lexically identical (such as Makefile and makefile), but end up being the two different files on the OS level. It cuts both ways. If you really see this as a problem, you should cut out uppercase from unix usage too. I don't think case should be enforced programmatically in either environment. There are too many situations where mixed case might be seen as a benefit. I try to stick to lower case letters unless the circumstances really beg for upper/mixed case. In general, I tend to base it on who is the intended consumer. If it's a person, spaces and capitalisation are used. If it's a program, underscores and lowercase.	[reply]
Re^7: move command by rovf (Priest) on Jul 13, 2009 at 06:58 UTC
If you really see this as a problem, you should cut out uppercase from unix usage too. Actually, I try to avoid upper case in filenames, no matter which OS I'm using, but I admit that there are cases where it really makes sense to use upper case letters as well. I agree with you in that any enforcement in this respect would be overkill. -- Ronald Fischer <ynnor@mm.st>	[reply] [d/l]