Piotr Jasiukajtis / estibi writes: > >> Well, I think it's worse then lack of order in the GNU's parameters. > > > > Most command line utilities in (Open)Solaris, and other UNIXes will take > > arguments in any sequence; the only caveat to that is when an option > > takes a parameter (eg. filename) which is usually bound to the option. I > > think that the phrase "in the GNU's parameters" needs clarification. > With "GNU's parameters" I mean: > GNU: > $ touch none > $ rm -r none -f > $
That's pretty silly, but I have a hard time seeing it as an actual bug in GNU (or really feature in Solaris). When you walk off the end of the functionality in the reference documentation (the man pages), an implementation should be free to do anything it wants, so long as the behavior is not outrageous. (I.e., rebooting the system for that command line would clearly be wrong. Accepting it as either an additional option or as a name of a file both seem reasonable to me.) The bug is in the user who doesn't understand how options work, doesn't read the man page, and types that. ;-} -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
