Foreach Quotes

. . . why not ask your congressman or woman to support universal background checks? Ask him or her to renew the ban on military-style assault weapons and high-capacity magazines. Offer a pink slip to any legislator who refuses to explain his or her lack of support for these common-sense measures. With rights come responsibilities. While we enjoy a right to bear arms, we have a societal obligation to do so responsibly and safely. We are, after all, responsible for each other. Our governing is done by the people and for the people.  It is in the best interest of the people, all the people, to apply common sense to the gun issue . . .

A forEach operation that does anything more than present the result of the computation performed by a stream is a “bad smell in code,” as is a lambda that mutates state.

How can we represent 'copy' example above in Java code? Here's one way to do it: CopyTask copy = new CopyTask(); Fileset fileset = new Fileset(); fileset.setDir("src_dir"); copy.setToDir("../new/dir"); copy.setFileset(fileset); copy.execute(); The code is almost the same, albeit a little longer than the original XML. So what's different? The answer is that the XML snippet introduces a special semantic construct for copying. If we could do it in Java it would look like this: copy("../new/dir") { fileset("src_dir"); } Can you see the difference? The code above (if it were possible in Java) is a special operator for copying files - similar to a for loop or a new foreach construct introduced in Java 5.