Re: [Plib-devel] Saitek X52 joystick with 34 buttons

[John D. <sf...@av...>]

I am reminded of the little girl who caught a tarantula and wanted
to keep it as a pet.  They make great pets;  they don't eat much,
they don't make noise, they don't smell, they don't bite, and they
exhibit a lot more interesting behavior than (say) a goldfish.  But
her father said "ewwwww, get that thing out of here".

She asked what was wrong.  He said "they give me the willies ...
too many legs."  She said that earlier she had caught a snake,
and he didn't approve of that either.  What's wrong with that?
Not enough legs?

I told her she should keep a pet tarantula *and* a pet snake.
That way there would be the right number of legs /on average/.

=============

In the case of plib I've just been told that anything less than a
full cockpit simulator isn't acceptable.  I've also told that
anything with more than 32 buttons isn't acceptable.  Hmmmm.

==========================

I'm also told the 34-buttons but is not a bug, but rather "an
application problem".

Horsefeathers.  The language spec says that an out-of-range shift
returns an _undefined_ result.

I try not to return undefined results from my code.  Customers
generally don't like that sort of thing.

With the amount of effort people have spent arguing about whether
it's a bug or not, we could have fixed the bug already.

On 01/02/2007 10:50 AM, Fay John F Dr CTR USAF AFSEO/SK wrote:

>>        .... didn't use STDLIB in the first place is that
>> when PLIB was first written, STDLIB was neither standard, nor
>> widespread, nor reliable.

I think the expiration date on that argument is long past.  The
stdlib is part of the language specification, and has been for
several years.  If there is any evidence that vector<bool> is not
reliable, you should report it through proper channels.

I say again:  with the amount of effort people have spent arguing
about whether it's a bug or not, we could have fixed the bug already.