Re: [MiNT] AHCC V4.11

[Thomas Jürges <thomas@senmut.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yo Henk,

On 2012-05-31 14:32, Henk Robbers wrote:
>> Maybe you could simply choose the mask depending on the OS AHCC
>> is running on (plain TOS/EmuTOS = uppercase, MiNT/MagiC =
>> lowercase), or let the user choose which mask is suited for his
>> configuration.
> 
> Yes, I'll do that. Next version :-)

out of curiosity, you are going to do which of the two?  :-)


As I view the case at the moment, there are two main players in the
game of file names and file masks and their representation in file
selectors:  the file system and the file selector.  Hence during any
given moment one could encounter one out of four combinations:

a) FS supports UPPER/lower case file names - file selector supports
UPPER/lower case file names
b) FS supports UPPER/lower case file names - file selector does not
support UPPER/lower case file names
c) FS does not support UPPER/lower case file names - file selector
supports UPPER/lower case file names
d) Neither support UPPER/lower case file names


I take it that everybody agrees on the obvious handling of situation
a).  :-)  The other three are a little more difficult to handle and I
leave the solving of those problems to the reader.  ;-)  - Well,
frankly said, I would rather take the very simplest approach and let
the user configure the behaviour when a file system or a file selector
does not handle the letter case properly.  Whatever is done in an
automated fashion will annoy pretty much the other 50% of the users.
But that is just my two cents worth.

Cheers,
	T.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iF4EAREIAAYFAk/H4TEACgkQSwr0ZkS0/dzH8AD+P1MEGcsnYbpXC91g/DaZqqJ7
mFVW44qizy34e407n2AA/3TTIHiaiv3/Hrabo8ICEWcbHCL1H5ZMjOYjNtcPDEpj
=FTtf
-----END PGP SIGNATURE-----