mccv - Latest Comments

Re: What is timestamp used for in all those Cassandra calls?

akku Asus Z99Fm — Tue, 03 Jan 2012 05:37:53 -0000

good job!

Re: What is timestamp used for in all those Cassandra calls?

VGP-BPS9A/B — Tue, 03 Jan 2012 05:35:07 -0000

Protect

Re: Exception Erasure

akku Asus Z99Fm — Tue, 03 Jan 2012 05:29:49 -0000

sfsf

Re: Exception Erasure

dell inspiron 1525 akku — Thu, 27 Oct 2011 02:33:54 -0000

Dieser Artikel war sehr gut geschrieben, ich danke Ihnen für den Austausch!

Re: Getting Started With The Talking Puffin Twitter API

Akku XPS M1330 — Thu, 18 Aug 2011 04:17:20 -0000

Ich überlegte einen anderen Laptop zu ändern, weil es zu schwer war, Hardware schlecht. Aber vor allem, weil die Batterie zu schnell. Dank zu teilen, geben Sie mir eine gute Wahl

Re: Things that are easier in Scala vol. 2

Akku XPS M1330 — Thu, 18 Aug 2011 02:10:36 -0000

Dieser Artikel war sehr gut geschrieben, ich danke Ihnen für den Austausch!:)

Re: What is timestamp used for in all those Cassandra calls?

akku dell — Mon, 25 Jul 2011 02:53:37 -0000

this is a good akku dell shop http://www.dellakku.de/

Re: You can’t clone superstars

medion akku — Wed, 08 Jun 2011 05:04:39 -0000

Medion Akku

Re: Getting Started With The Talking Puffin Twitter API

medion akku — Wed, 08 Jun 2011 05:03:08 -0000

making stuff simple and easy to use (traversing firewalls

Re: Getting Started With The Talking Puffin Twitter API

drivers — Mon, 04 Oct 2010 01:28:35 -0000

That's very helpful and interesting! I really like this article.

Re: Getting Started With The Talking Puffin Twitter API

laptop battery — Thu, 26 Aug 2010 02:03:29 -0000

making stuff simple and easy to use (traversing firewalls is pretty important in this case).

Re: Scala exceptions vs. pattern matching

chris_lewis — Fri, 09 Apr 2010 11:04:36 -0000

There's more to monadic error handling than just forcing the developer to state via verbosity that he is aware of a potential error. Note that scala.Option defines a few higher-order functions, namely foreach, filter, map, and flatMap: http://www.scala-lang.org/docu...

These allow us to pass behavior to an Option instance that will only execute if it has a value (ie an instance of Some). For example, to get a collection of the status updates:

val matches = new HttpXMLMatches()
val url = "http://twitter.com/statuses/pu..."
matches.getXML(url).map { _ \\ "status" \ "text" map { _ text } }

This results in a Some[Seq[String]] of the text nodes of the status updates. You could also use for comprehensions:

for(xml <- matches.getXML(url)) yield (xml \\ "status" \ "text" map { _ text })

Or if you just want to do some side-effecting action, like printing the text:

for(xml <- matches.getXML(url)) { println(xml \\ "status" \ "text" text) }

I'm still trying to work out some guidelines as to when monadic handling is preferable to exceptions.

Re: Things that are easier in Scala vol. 2

astubbs — Fri, 07 Aug 2009 07:32:39 -0000

Ah yes of course - I remembered that soon after I posted :)

Re: Things that are easier in Scala vol. 2

mccv — Wed, 05 Aug 2009 15:23:54 -0000

Not sure on the exact question... all of the Java ones are checked exceptions. Scala doesn't force you to catch them, so I didn't. Realistically there should by a try block somewhere to handle Thrift and Cassandra errors.

Re: Things that are easier in Scala vol 1

astubbs — Wed, 05 Aug 2009 12:54:11 -0000

A couple of things..

a) If you make it a trait - you can mix it in and just call tryNTimes without the object classifier - that's closer still, right?

b) You can still retry and function, by creating a curried function or function pointer and passing that in:

def myFunc(s:String) { println(s) }
def toRetry = myFunc("Hi!")
tryNTimes(toRetry, 5)

right? I used this style in some test code I just wrote, where I had a test sequence that applied to several code blocks, some that took params.

Re: Things that are easier in Scala vol. 2

astubbs — Wed, 05 Aug 2009 12:44:21 -0000

Nice - I like. Were all those exceptions run time exceptions - is that why you aren't catching them?

Re: Running Scala specs tests in Maven with JUnit 4

mccv — Mon, 27 Jul 2009 11:01:50 -0000

Excellent, that would be quite a bit nicer. Having the object/class pair is a bit clunky... Overall the framework is very nice though.

Re: Running Scala specs tests in Maven with JUnit 4

etorreborre — Sun, 26 Jul 2009 20:05:59 -0000

Hi Mark,

Thanks for your post.

2 tips for making your specification even more concise (with specs.1.6.0-SNAPSHOT or 1.5.1 SNAPSHOT):

This will make your specification class a JUnit test:
class BasicCassandra extends SpecificationWithJUnit { ... }

It is still runnable in the console with:

scala -cp <...> run BasicCassandra

And you can write (if you like it):

cass.connect().before
cass.close().after

Cheers,

Eric.

Re: Things that are easier in Scala vol 1

khrabrov — Sat, 23 May 2009 00:26:57 -0000

Wow! Just in time as I'm contemplating retrying slurping of a user's tweets. I'll add something like "requeue" as the final result where all N tries failed.