Well, it seems like Perl treats STDIN as a file handle, always (kinda like "stdin" and "stdout" and "stderr" are always pre-defined as "FILE *" thingies in C, and you shouldn't try to use them for other things). Using STDIN as the name/namespace for a package/object of your own design won't work, "so don't do that."

I guess I'm not particularly sensitive towards this issue (i.e. I don't have a problem with it); if you get by with calling your package "Stdin" or "MYSTDIN" or some such, where's the trouble? What would a package named "STDIN" get you that you can't get some other way? (I really would be curious to know...)