Comments for Along Came Betty http://blog.darevay.com You know, software and some other stuff like maybe guitar or something Wed, 27 Jan 2010 13:24:02 +0000 http://wordpress.org/?v=2.9 hourly 1 Comment on About by Inigo http://blog.darevay.com/about/comment-page-1/#comment-3642 Inigo Wed, 27 Jan 2010 13:24:02 +0000 http://blog.darevay.com/?page_id=2#comment-3642 Hello, I'm interested in using ROOSCALOO but I can not run. I can compile and create the Jar. Now, I run from the command line but I don't know how to works it. Thanks a lot Hello,
I’m interested in using ROOSCALOO but I can not run. I can compile and create the Jar. Now, I run from the command line but I don’t know how to works it.

Thanks a lot

]]> Comment on The Eclipse Reconciler by Swati http://blog.darevay.com/2007/11/the-eclipse-reconciler/comment-page-1/#comment-3640 Swati Tue, 26 Jan 2010 18:47:10 +0000 http://blog.darevay.com/?p=8#comment-3640 Hi, Thanks a lot for sharing the understanding. It helped me get back in touch with what I had worked on long time ago. Eager to check other articles on your blog. Swati Hi,
Thanks a lot for sharing the understanding. It helped me get back in touch with what I had worked on long time ago.

Eager to check other articles on your blog.

Swati

]]> Comment on Can anything I write here help open source? by Nicholas http://blog.darevay.com/2009/11/can-anything-i-write-here-help-open-source/comment-page-1/#comment-3105 Nicholas Tue, 24 Nov 2009 08:39:45 +0000 http://blog.darevay.com/?p=223#comment-3105 Blog traffic is super-gratifying. Keep it all here. ;) Blog traffic is super-gratifying. Keep it all here. ;)

]]> Comment on Remedial Scala: Interpreting Scala from Scala by philip andrew http://blog.darevay.com/2009/01/remedial-scala-interpreting-scala-from-scala/comment-page-1/#comment-2595 philip andrew Mon, 12 Oct 2009 15:02:49 +0000 http://blog.darevay.com/?p=183#comment-2595 Hi, any updates on interpreter? I want to do this for some scala code and keep the state of the interpreter hanging around. Hi, any updates on interpreter? I want to do this for some scala code and keep the state of the interpreter hanging around.

]]> Comment on Importing Multiple WSDLs with Maven by asaf http://blog.darevay.com/2009/03/importing-multiple-wsdls-with-maven/comment-page-1/#comment-1898 asaf Sun, 02 Aug 2009 11:28:52 +0000 http://blog.darevay.com/?p=198#comment-1898 Dude, you totally aced it with your solution to this bug. Apparently this guys *still* haven't the bug (they upgraded to 1.12 version) Dude, you totally aced it with your solution to this bug.
Apparently this guys *still* haven’t the bug (they upgraded to 1.12 version)

]]> Comment on Ten Little Soul Crushing Features of Java by Dario http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/comment-page-1/#comment-1837 Dario Wed, 22 Jul 2009 15:43:18 +0000 http://blog.darevay.com/?p=205#comment-1837 IllegalArgumentException is to be thrown when argument is illegal or inappropiate, and it's a RuntimeException (About RuntimeException, since every method can throw it, none is required to tell, so it's easy to miss that or any of its subclasses) MalformedURLException is more strict, specifically it hasn't a recognizable protocol or the url string couldn't be parsed. It's a IOException subclass, no a RuntimeException one, so it has to be declared and thus it won't jump by surprise. Beside RuntimeException family (like NullPointer, ClassCast, IndexOutOfBounds...), MalformedURLException seems full of sense to me... IllegalArgumentException is to be thrown when argument is illegal or inappropiate, and it’s a RuntimeException (About RuntimeException, since every method can throw it, none is required to tell, so it’s easy to miss that or any of its subclasses)
MalformedURLException is more strict, specifically it hasn’t a recognizable protocol or the url string couldn’t be parsed. It’s a IOException subclass, no a RuntimeException one, so it has to be declared and thus it won’t jump by surprise.
Beside RuntimeException family (like NullPointer, ClassCast, IndexOutOfBounds…), MalformedURLException seems full of sense to me…

]]> Comment on Ten Little Soul Crushing Features of Java by dave http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/comment-page-1/#comment-1642 dave Fri, 08 May 2009 17:31:09 +0000 http://blog.darevay.com/?p=205#comment-1642 <a href="#comment-1641" rel="nofollow">@Svend</a> join() can be implemented with concat(), but they're not the same. I want to write: ", ".join(Arrays.asList("Jim", "Bob", "Al")); and get: "Jim, Bob, Al". You're code for reading a file is fine, but, again it's a matter of convenience. Rather than writing that function over and over from project to project I want it built in: String s = String.fromFile("test.txt"); or something like that. I've just been spoiled by scripting languages I guess. @Svend
join() can be implemented with concat(), but they’re not the same. I want to write:
“, “.join(Arrays.asList(“Jim”, “Bob”, “Al”));
and get:
“Jim, Bob, Al”.

You’re code for reading a file is fine, but, again it’s a matter of convenience. Rather than writing that function over and over from project to project I want it built in:
String s = String.fromFile(“test.txt”);
or something like that.

I’ve just been spoiled by scripting languages I guess.

]]> Comment on Ten Little Soul Crushing Features of Java by Svend http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/comment-page-1/#comment-1641 Svend Fri, 08 May 2009 17:22:38 +0000 http://blog.darevay.com/?p=205#comment-1641 1. Isn't that what String.concat(String) is for? 10. InputStream and Reader are streaming interfaces, which means that they can have more content than you can fit in an array. It sounds like you're talking about file based input stream or readers, in which case you can do this (provided your file length is smaller than 2GB): method(File file) { FileInputStream fis = new FileInputStream(file); byte[] bytes = new byte[(int)file.length()); fis.read(bytes); } 1. Isn’t that what String.concat(String) is for?
10. InputStream and Reader are streaming interfaces, which means that they can have more content than you can fit in an array. It sounds like you’re talking about file based input stream or readers, in which case you can do this (provided your file length is smaller than 2GB):
method(File file) {
FileInputStream fis = new FileInputStream(file);
byte[] bytes = new byte[(int)file.length());
fis.read(bytes);
}

]]> Comment on Ten Little Soul Crushing Features of Java by dave http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/comment-page-1/#comment-1162 dave Sun, 19 Apr 2009 12:09:25 +0000 http://blog.darevay.com/?p=205#comment-1162 Yep. It's fixed now. Thanks for catching that. Yep. It’s fixed now. Thanks for catching that.

]]> Comment on Ten Little Soul Crushing Features of Java by mkneissl http://blog.darevay.com/2009/04/ten-little-soul-crushing-features-of-java/comment-page-1/#comment-1159 mkneissl Sun, 19 Apr 2009 11:51:36 +0000 http://blog.darevay.com/?p=205#comment-1159 Mostly agree to your list, but shouldn't 6) read "non-empty directory"? Mostly agree to your list, but shouldn’t 6) read “non-empty directory”?

]]>