Steve Z wrote:
It is, nonetheless, a legitimate character for CMS filenames.
I know that. I acknowledged that fact it in my reply:
"Yes, it's a legal filename character as far as CMS is
concerned, that is true. But its use in CMS filenames
is VERY atypical. It's like using blanks in filenames
on *nix: such filenames *are* supported, but their use
is VERY atypical and thus discouraged."
They are on the SCRIPT 191 disk.
If there are indeed filenames on the "SCRIPT 191 disk"(?) (I'm guessing that's a VM SixPack thing?) with names containing the "#" character, then IMHO those files should be renamed to something else.
[...]
If you don't want to fix it or don't think it's a bug,
that's fine. Just sharing what I found.
Understood and appreciated. Bug reports are always welcome. As I said, I *personally* don't feel it's worth fixing, but my opinion on the matter is of course only that of one person. The other members of the Hercules development team (as well as possibly other users too!) might feel differently. They might feel, like you, that it is indeed a bug that should indeed be fixed. I honestly don't know! I don't speak for the entire Hercules development team. I'm not the boss. We have no boss. My opinion does not rule the day.
The point is, if you honestly feel it is something that should be fixed, then IMO you should officially report it as such so that it gets fixed. Mentioning it here is fine, but if you want it fixed, you should take the time to officially report it. That's all I'm saying. <shrug>
Cool?
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
