http://www.haloscan.com/ Latest comments for holygoat. Syndicated by HaloScan http://www.haloscan.com/ http://www.haloscan.com/halolink.gif http://www.haloscan.com/ 88 31 Commenting Powered by HaloScan.com http://www.haloscan.com/comments/holygoat/2006_08_03_1/?src=hsr#296326 Sun, 15 Nov 2009 21:51:14 +0000 http://www.haloscan.com/comments/holygoat/2006_08_03_1/?src=hsrs#296326 http://www.haloscan.com/comments/holygoat/2006_08_03_1/?src=hsrs#296326 You must have sensitive teeth, that's why you are experiencing that pain. It is good to see your dentist immediately rather than feeling another pain for a couple of weeks again. http://www.haloscan.com/comments/holygoat/2009_06_08_1/?src=hsr#289207 Tue, 09 Jun 2009 12:20:40 +0000 http://www.haloscan.com/comments/holygoat/2009_06_08_1/?src=hsrs#289207 http://www.haloscan.com/comments/holygoat/2009_06_08_1/?src=hsrs#289207 Of course, one interesting corollary of this is that the "best" technology is very much in the eye of the beholder. You and I could be looking at an identical problem on identical hardware with identical software stacks and could still have very different ideas of what works best For you, it might be quickest to solve the problem in C or Lisp, while for me it would be quicker to use Perl, just be http://www.haloscan.com/comments/holygoat/2009_03_31_2/?src=hsr#288850 Sun, 17 May 2009 12:22:39 +0000 http://www.haloscan.com/comments/holygoat/2009_03_31_2/?src=hsrs#288850 http://www.haloscan.com/comments/holygoat/2009_03_31_2/?src=hsrs#288850 I dont follow? http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsr#287301 Thu, 16 Apr 2009 23:12:21 +0000 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287301 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287301 @Steve: I decided against explicit preprocessing because an external macro language is by definition outside of the language in which I'm working. It doesn't integrate with Eclipse, for example. The subject of my rant was that the Java language itself doesn't include a feature like this, which has proved itself to be useful in countless situations throughout the last 25+ years. If I reintegrate... http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsr#287290 Thu, 16 Apr 2009 17:09:05 +0000 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287290 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287290 To me this sounds like a perfect example of where you should be using Dependency Injection via Google Guice. You could package the whole thing into one .jar/.war/.whatever and have Guice pick the correct implementation on runtime depending on the container you use. If you wa http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsr#287288 Thu, 16 Apr 2009 16:57:38 +0000 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287288 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287288 Branching on simple comparisons to final static values will be compiled *as though* explicit conditional compilation were part of the language. FYI. If you like, go ahead and check it out yourself using javap. http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsr#287282 Thu, 16 Apr 2009 10:23:06 +0000 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287282 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287282 Its best to ignore the fact that you are using the specific classes of application servers, something which is not standards compliant and hence not portable. Instead the solution is to understand that although the class needs to be there at compile time to resole the dependency it does not need to be there at runtime if you don't use it. Using Class.forName will load the appropriate version of... http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsr#287281 Thu, 16 Apr 2009 10:01:46 +0000 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287281 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287281 Just use AspectJ and AJDT if you're using eclipse; it will give you all the Holy Handgranate power you will ever need to f*ck other people's code. I love it. http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsr#287279 Thu, 16 Apr 2009 08:28:15 +0000 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287279 http://www.haloscan.com/comments/holygoat/2009_03_21_1/?src=hsrs#287279 If you want conditional compilation so badly why don't use just use a macro language to preprocess your .java files? http://www.haloscan.com/comments/holygoat/2009_03_26_1/?src=hsr#286993 Thu, 02 Apr 2009 17:30:27 +0000 http://www.haloscan.com/comments/holygoat/2009_03_26_1/?src=hsrs#286993 http://www.haloscan.com/comments/holygoat/2009_03_26_1/?src=hsrs#286993 I was working on my own MD5 implementation in Clojure when I stumbled upon this one. One thing I learned is that the MD5 sometimes will be 31 characters long instead of the normal 32. For example. this happens on the md5 of "vasdf". In such cases you will need to pad a "0" in front of the string.