That doesn’t sound like a great idea to me, unless all the
methods of Hash
are useful in an “options” context. (They may well be; I’ve
had very small
exposure to GetoptLong.)
I disagree. Why must all the options be useful? I’m sure more than one
person here has subclassed a base class where we never really expect to use
methods x, y and z. Not that they wouldn’t work, you just wouldn’t use
As it stands now, GetoptLong acts like a cousin of Hash, rather than a
child. Looks like a Hash, smells like a Hash but…it’s not a Hash. This
only leads to confusion, IMHO. Besides, it already sounds like more than
one person is resolving their problems with GetoptLong by slapping the
results into a Hash anyway. I know I have.
I guess I’m at the .03 cent stage now.
I’m just saying this because Java made a hash (ha ha) of
Stack class be extending Vector. Simply wrong.
On 1 Aug 2002, at 15:41, Paul Duncan wrote:
I find myself converting the results of option parsing into
Let’s take it a step further. Scrap the current
implementation and make
GetoptLong a subclass of Hash.
Just my .02.