P Kishor wrote:
On 11/28/06, John Stanton <[EMAIL PROTECTED]> wrote:
If you use an extension greater than 3 chars you violate rules for some
existing file systems and reduce portability. You can also make it
difficult to parse the extension when it is used to type the file.
we are going a bit off-thread here, but violating the file system rule
(in this case, Windows) is precisely why I use an extension greater
that 3 chars. For example, .db extension is used by several other
programs -- Windows itself uses .db extension for thumbnails it
generates for pictures inside a folder. I want to get above that
riff-raff. The stupid system just lists my databases as "SQLITE File."
Good enough for me.
As far as portability is concerned -- my world revolves around Unixes,
in particular Mac OS X, some Linux variants, and Windows. I have never
had any portability issues with foo.sqlite.
In medecine the Hippocratic Oath requires "First, do no harm". Not a
bad principle for IT design also.
I think, in good health, the first principle should be, don't expose
yourself to ills. By making my extension illegible to anything but
SQLite, I am not even getting in the fray.
Since we're already off-topic. :-D
I'm sure you are already aware of this, just pointing it out in context
so those that aren't have a heads up.
Just a bit of warning, as it has bitten a few in the bum, about >3
character extensions under the NT+ variants.. They can and will bite
you, for instance:
dir *.sql
Will list not only *.sql files, but *.sqlite too.
Imagine:
del *.sql
Deleting all your *.sqlite files. Whoopsie..
--
Craig Morrison
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://pse.2cah.com
Controlling pseudoephedrine purchases.
http://www.mtsprofessional.com/
A Win32 email server that works for You.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
