Proceeding with lookup, showing first example

Shortening the lines

Enough of spring

Reference to spring

Fixing examples so their BEGIN starts with space

Slightly different way to do call-outs. With this style the PDF printed from ODF document at least contain the right texts

Making the examples more appropriate for the book

Need a space before BEGIN now

No need for imports

Yet another example of spring autoconfiguration

Adding the lookup version

Showing how such a general registry might look like

Prefer autowire mode

Spring example runs

Spring version that compiles, but does not run

Shortening lines

Made compilable

Simplified with duplication of the code ;-)

Solution with properties

Making anagrams visible

Example with registration methods is working

GUI for anagrams

Simple scrambler

Static world library

Defining APIs for the modular interfaces

Not using deprecated method

Showing regular Anagram game

TopManager example taken from sources

No, NOI18N

Merge: Geertjan's changes to the end of the chapter

to the end of daily_life

Making the example with MixedClass vs. NonMixed solution more real, so it can be unit tested

Splitting Factorial into own class, so Andrei does not need to complain about it having static modifier

Making sure the code survives negative inputs

Show the definition of the cnt variable

reading needs to synchronize as well

Renaming to parallel

Misuses are OK

Using public modifiers

Shortening long line

Reimplementing the lookups once again

More tests, fixing closing tag

Parameter renamed to seq

Using a method that is named to indicate what is its purpose, instead of magic seq.length() < 1024

Use encryptChar

Counting writer does not need author tag

The XMMS example now extracts the code snippets from real files that do compile

Sample polishing requested by Andrei and Jesse. In spite I do not agree it is important - but I do not have power to describe that it is not important. Maybe in a blog.

Jesse wanted to have better example of InstanceProvider. Done, but it is also more complicated: http://wiki.apidesign.org/index.php/A_Method_Addition_Lover's_Heaven

Addressing issues at http://wiki.apidesign.org/index.php/Allow_Access_Only_From_Friend_Code

Cleaning just the sources, not more, building just samples and not other ant tasks

Lines were too long

Merge: Some Patrick's one liner fixes

daily life polishing through 3500

review31: Providing randomized Arithmetica test to verify inconsistencies with version 1.0

Enhancing the example to contain randomized that to verify consistency with previous implementation

Visitor.visit(with self) turned into sample

Adding tests also for 3.0 version of the API

Incorporating Patrick's changes. I am not reall sure about the changes after the war, it is really 'or' it cannot be 'and'. I will change that when I do the reading through the whole chapter.

polishing lines 500-1000

Going through the suggar section

Fixing compilation errors

Third version and tests for client provider visitor

First two versions of client provider Visitor

Complicated dispatch code in Minus version 3.0

Proper dispatch in Real

Wrapper around Real is OK

Testing version 3.0

Need to copy the code also to 3.0 version

It always surprises me how things change when one really tries to implemente them. The whole approach with non-monotinic evolution was uncompilable. We need a common super type for all the visitors\!

Clean definition of the version using interfaces

Expose as less as possible - making constructor of Expression package private

In order to provide better navigation in the Visitor examples, I will prefix them with a number

Last clashing code section for now. Time to sleep

Duplicated code section

Closing up examples of visitor based on abstract class

There was some mischmash between abstractclass and unknownvisit, hopefully fixing it

default traversal described

Fix broken compilation

visitUnknown method introduced

Visitor pattern with abstract class is relatively good

Example with non-extensible visitor

Changed to match the example in the book

Full coverage is not enough

Adding example, however only a sketch, of possible runtime check between alternative versions

Merge: Geertjan's changs up to 2000

up to line 2000

Checking that all examples pair the opening and closing brackets

Adding example with factory method for unsynchronized StringBuffer

Yet another use of Arithmetica

Another use for Arithmetica

Using Arithmetica for yet another example

Alternative behaviour with constructor described on Arithmetica example

Improved to look better in the book code sample

Shortening too long line

Design part is cleared from the non-colorized code snippets

Special project for inidividual samples, used to show code that can be called only from test

Example showing that factory methods have greater flexibility when typing with generics

Build needs to succeed

Line was too long

All TBDs from theory section are resolved

Example of append(StringBuffer)

Another uncompilable example, now it shows problems with double return type

Wild import

Sample code to work with filesystem layers

Beautifies keywords, comments and method names.

Truncating to 75 characters

Truncating all examples to 80 characters per line

Merge: Geertjan's changes

up to line 1000

Adding targets to the build script to also create the samples, make sure they compile and tests execute

Merge: Patrick's fixes

part 2 of polishing "review2" areas

Accepting Jesse's edits

Routine edits in Determining What Makes a Good API.

Merge: Patrick's edits

2nd batch of polishing of review2

We know how to build the source zip file

We are able to run all tests from all the projects

Excluding NetBeans Module which requires NetBeans platform somewhere around