Good titles on your list, and the recommendations, so (in my best
consultant's voice) it depends on your perceived gaps and passions. For the
use case you described, I tend to like things that kick me out of my ruts.
*Prefactoring* (by Ken Pugh, O'Reilly) is an interesting take on enabling
chan
+1
On Mar 2, 3:54 am, Kevin Wright wrote:
> Learn in a more suitable language first and backport your knowledge.
That IMHO is by far the largest benefit; it's easier to learn new
concepts when expressed in a way that focuses on their essence,
instead of the accidental complexity of some language
And Ryan's comment raises an interesting possibility for next year's
JPR.
We normally have lightning-talk style summaries on Monday evening of
the day's activities.
This year, we had some themes that seemed to continue through the
week's afternoon code rodeos; so what do the attendees think of
pl
According to coverage at
http://arstechnica.com/apple/reviews/2009/08/mac-os-x-10-6.ars/10
, Snow Leopard, the latest version of Mac OS X, added "blocks" to C.
The article illustrates this new language construct with the by-now
canonical ARM and home-grown-control-structure examples.
Hey, Java!
Micro Focus, as in COBOL, that is. So now the speculation will run
rampant again as to whether Our Favorite Language is headed the way of
the dinosaur...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "The
Java Posse
The discussion of Pair, Triple, Tuple4..Tuple22 etc. makes me wonder
if this isn't too much of a solution. After writing:
Tuple t = someObject.someMethod();
the caller still may need to do something like:
String s = t._1(); // or "first" or "left" or whatever...
int i = t._2(); //
Thanks for posting that!
(no closing tag... I'm still chuckling silently!)
-jn-
On Feb 9, 10:00 pm, Christian Catchpole
wrote:
> This link cliams..
>
> 22 is the number of partitions of 8, and 8 is the largest cube in the
> Fibonacci sequence, and the Fibonacci sequence is the most popular FP
In the interest of fairness to Good Old Java, this is not as much of a
show-stopper as the examples make it appear.
On Feb 13, 10:14 pm, Jeff Grigg wrote:
> The problem is that when you use method chaining on classes that
> extend other classes and which add methods, you MUST always call
> subcl
