K
Kelsey Bjarnason
I'm online at the moment, trying to help someone with a programming
problem. His code, which isn't as bad as it could be, is trying to open a
file "file.in".
The file exists, is called "file.in" and is in the right place - but the
code won't open it - can't find the file.
Say what? Can't find the file? But it's right there, with the right
name, so why can't it find it?
Some poking around reveals the problem. First, the file was created with
notepad - which insists upon appending a .txt to everything. Fine so
far... but Windows Explorer *shows* the file as being simply "file.in" -
because the default setting is to hide file extensions.
So the user _sees_ "file.in" and can't tell what's going wrong - the fact
that the file is actually called "file.in.txt" and will never be found
with his application.
Ah, ease of use. Doesn't get any better than this.
problem. His code, which isn't as bad as it could be, is trying to open a
file "file.in".
The file exists, is called "file.in" and is in the right place - but the
code won't open it - can't find the file.
Say what? Can't find the file? But it's right there, with the right
name, so why can't it find it?
Some poking around reveals the problem. First, the file was created with
notepad - which insists upon appending a .txt to everything. Fine so
far... but Windows Explorer *shows* the file as being simply "file.in" -
because the default setting is to hide file extensions.
So the user _sees_ "file.in" and can't tell what's going wrong - the fact
that the file is actually called "file.in.txt" and will never be found
with his application.
Ah, ease of use. Doesn't get any better than this.