After a lot of head scratching, hair pulling, profanities, and other assorted frustrations, and finally spotting the short blurb buried in the getopt_long manpage to explain this behavior, I'm at a bit of a loss on how to proceed, and hoping someone that's more familiar with POSIX, SUS, etc. can offer some insight here:
Apparently getopt_long_only() allows '-longoption' and '--longoption', however getopt_long() does not comply with POSIX (I'm not a standards lawyer, so I'm not exactly sure what the issue is, other than I've been told 'don't use it (for stuff expected to comply w/ POSIX, SUS, etc.)'). I'm curious for this behavior, as it pretty much means any short option cannot use any letters that start a long option. At first glance, this seems somewhat less than useful, so I'm curious to understand the rationale behind it (or if there's an open ARC case I can look at, that'll work to). So I'm a bit stuck then how to add compatibility long options while not breaking POSIX, and it looks like (unless I'm missing something) that Opensolaris does not provide any way to do that. Can someone not only tell me I'm wrong, but what the answer is? :) _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
