Forgot your password?

Comment: Re:We've come a long way (Score 1) 146

by spitzak (#46710515) Attached to: Born To RUN: Dartmouth Throwing BASIC a 50th B-Day Party

So you can declare a variable of type MyClass called myClass, or a method that returns a MyClass called myClass().

In most languages this would be impossible if case was not preserved by lexical scanning (there are a few languages where the intention can be distinguished by syntax, which would allow the class name and method to be exactly the same, and then case sensitivity may be less of a problem).

Another huge problem with case insensitivity is that the rules get really complex once you get out of ASCII-only, and different interpretations of the rules in effect mean you have literally thousands of actually different syntaxes.

Comment: Re:informal poll (Score 1) 641

by spitzak (#46662945) Attached to: Linus Torvalds Suspends Key Linux Developer

My home computer is dual boot with Ubuntu (12?) and Windows 7, and I never use Windows on it (I know because there is a bug and it does not work with the serial keyboard, so I have to dig out and plug in the USB keyboard that came with the machine if I want to boot it into Windows, and right now I don't even know where that keyboard is (ps the bug is strange: only the login does not work. Once you log in the serial keyboard works just fine)). We also have a much older iMac and a couple Android tablets and one iPad, an ancient iMac PowerPC used to play music on the stereo, and an ASUS Linux netbook that amazingly still works and is used by visitors more than I would expect.

Comment: Re:It's been bisected and confirmed (Score 1) 266

by spitzak (#46612235) Attached to: Ask Slashdot: How To Handle Unfixed Linux Accessibility Bugs?

Sorry, a mouse button is a key for anybody in the real world. It even has it's own keysym values in X.

Also as pointed out, OS/X and Windows, and earlier verisons of X, worked this way. If this is really somebody saying "mouse buttons are not keys and I will obey the text literally" then that is really sad.

From the patch description this sounds like an accidental change, not deliberate. But beyond that it is hard to figure out what needs to be fixed. It sounds like there is a null pointer dereference, but only when the X server is shutting down. That's pretty minor and in fact something I know commercial software would ignore.

Comment: Re:It's been bisected and confirmed (Score 2) 266

by spitzak (#46607745) Attached to: Ask Slashdot: How To Handle Unfixed Linux Accessibility Bugs?

I'll bet this is going to be patched in the git repositor within a half hour.

But I'm not sure if posting Slashdot stories is the best way to get a bug fixed. But if it is the only one that works, might as well do it.

I still feel the original poster should have put *something* on that bug report in all the time since January 16th!

Comment: Re:It's been bisected and confirmed (Score 5, Informative) 266

by spitzak (#46607729) Attached to: Ask Slashdot: How To Handle Unfixed Linux Accessibility Bugs?

Goddamn that was painful, but I found the actual patch:

I would say it is rather shocking that this Peter Hutterer actually did about 90% of the work, then posted something that is not a clue as to how to see the answer.

And that the original poster (who I assume made this Slashdot story) did not post any followup for 3 months, probably leading Peter to forget all about fixing this.

Comment: It's been bisected and confirmed (Score 4, Insightful) 266

by spitzak (#46607663) Attached to: Ask Slashdot: How To Handle Unfixed Linux Accessibility Bugs?

Somebody has already narrowed the problem down to specific patch:

Comment 7 Peter Hutterer 2014-01-16 05:43:43 UTC

bisected to this commit:

commit 11319a922575f1da1d3c5774728c0dee12bab069
Author: Peter Hutterer
Date: Thu Oct 11 16:03:33 2012 +1000

        xkb: ProcesssPointerEvent must work on the VCP if it gets the VCP

It would help if that number was a link to the git log.

Time is an illusion perpetrated by the manufacturers of space.