Test Infected, Agile Methodology oriented developer. Developing in Java, C#, C++, and Python. (I'll even admit to VB6 in my past as well.)

2d
awarded Famous Question
Apr
22
comment How should we go about users "rage quitting" Stack Overflow?
I like comments where people tell the questioner, "please post your code", or other very specific suggestions about how to correct what is lacking. (Disclaimer: I have no idea how Echohonest works.) In looking at his question, I felt he actually gave all the information needed: he posted a URL which according to his understanding of the docs should have returned results, but didn't. That seems like all the info needed to frame the question. So either giving a specific suggestion for clarification or leaving a post alone (when you don't know the technology) may be the best policy.
Apr
17
awarded Constituent
Apr
17
awarded Caucus
Apr
9
awarded Autobiographer
Apr
9
awarded Autobiographer
Apr
9
awarded Autobiographer
Apr
9
awarded Supporter
Apr
8
awarded Notable Question
Apr
7
awarded Good Question
Apr
7
awarded Popular Question
Apr
6
comment Why is returning a Java object reference so much slower than returning a primitive
Aleksey: actually what was the difference between 1.1.1 Blackhole code and the 1.7.1 code?
Apr
6
accepted Why is returning a Java object reference so much slower than returning a primitive
Apr
6
comment Why is returning a Java object reference so much slower than returning a primitive
Thanks for the detailed explanation. The 1.7.1 version of JMH does indeed show virtually the same times. If I had started with that version, I could have avoided the whole question. As I wrote, I started by comparing different look up functions, which were not "infrastructure bound", and then when I rechecked the function I actually wrote against the previous tests, I saw this big difference. The purpose of asking the question was to find out what was the difference. (Trust me, I started trying to decompile, etc to see what was happening.)
Apr
6
revised Why is returning a Java object reference so much slower than returning a primitive
added download link for code and instructions to run
Apr
6
awarded Nice Question
Apr
6
revised Why is returning a Java object reference so much slower than returning a primitive
specify JDK version
Apr
6
asked Why is returning a Java object reference so much slower than returning a primitive
Feb
4
awarded Popular Question
Jan
29
comment Java PathMatcher: GLOB patterns are inconsistent on UNIX/Windows
I was having some problems also with the PathMatcher on Windows. I had to use "/" as a separator (i.e. same as Unix), and then it seemed to work fine. I tried a similar pattern as you did, i.e. **/{dir1/dir2/dir3/, dir4} and it matched as expected. What I see in the debugger, is that under the hood, it reversed the slashes (to match Windows separator) and it gets converted to a RegExp pattern. So it appears to be doing a Regular Expression match against the path string.
1 2 3 4 5