concept place in category groovy

This is an excerpt from Manning's book Groovy in Action, Second Edition.
These self-explanatory examples give an impression of what’s possible with strings in Groovy. If you’ve ever worked with other scripting languages, you may notice that a useful piece of functionality is missing from listing 3.5: changing a string in place. Groovy cannot do so because it works on instances of java.lang.String and obeys Java’s invariant of strings being immutable.
Before you say “What a lame excuse!” here’s Groovy’s answer to changing strings: although you cannot work on String, you can still work on StringBuffer![15] On a StringBuffer, you can work with the << (left shift) operator for appending and the subscript operator for in-place assignments. Using the << operator on String returns a StringBuffer. Here’s the StringBuffer equivalent to listing 3.5:
The widespread use of XML and worldwide adoption of Java took place at about the same time. This may be one of the reasons why the Java platform developed such excellent support for working with XML. Not only are there the built-in SAX and DOM APIs, but many other libraries have appeared over time for parsing and creating XML and for working with it using standards such as XPath.
In-place processing is the conventional means of XML processing. It uses the XmlParser to retrieve a tree of nodes. These nodes reside in memory and can be rearranged, copied, or deleted, and their attributes can be changed. We’ll use this approach to generate an HTML report for keeping track of our Groovy learning activities.