Author: rick reynolds (---.nimh.nih.gov)
Date: 04-21-09 16:15
Hi Mathieu,
It is neither a bug nor a feature, really.
There is no mention of ".NII" in the specification. There was
never any intention of allowing it. Maybe that is just because
no one had thought about it or cared.
There have never been problems reported from this; you are the
first to even mention it (that I know of). So if after all
these years, the first person to bring it up calls it unlikely,
what is the point of adding more complexity to the file names
(we already have 6 extensions)?
Note that not everyone uses the C library, so each code base
would need to be changed, and for something not currently in
the spec. There are many groups that have implemented this,
it is a lot to tell them all to go change their code.
Maybe you know of a systemic reason to allow that (such as mac
filesystems jumping between cases, which they do to some degree).
Do you know of something like that?
- rick
|
|
