Unified formatting in parser
Renamed methods that initially push values to the stack.

Renamed methods - generatePushConstant
                - generateBooleanConstant
                - generatePushIdent
to 'pushX' to better reflect the behaviour of the methods.
Parser generates conditional jump for if-statements
pushConstantBool uses pushConstantNumber to push constants

This removes a bug that didn't save boolean values on
the address stack
Output now writing correctly
Removed unnecessary code in Output.

Java Conventions say you only should use 'this.' when needed.
Constructor with null-initialization is equal to default constructor.
Replaced String.format(..) with string concatenation

Concatenation is better readable and more efficient.
Java even tries to replace concatenation with StringBuilder
during compilation, if suitable.

'Java's String.format works like so:
  1. it parses the format string, exploding into a list of format
     chunks
  2. it iterates the format chunks, rendering into a StringBuilder,
     which is basically an array that resizes itself as necessary, by
     copying into a new array. this is necessary because we don't yet
     know how large to allocate the final String
  3. StringBuilder.toString() copies his internal buffer into a new
     String'

Source:
http://stackoverflow.com/questions/513600/should-i-use-javas-string-fo
rmat-if-performance-is-important

So try to avoid String.format(..) where possible.
Scanner handles EOF correctly now.

Reintroduced the IOException when requesting a new morpheme when the
EOF morpheme has already been returned.

Boolean eofReached was set too early and default state was
initialized with the already processed last character in case
of an EOFException.
HALT-Command is generated now at end of parsing
Addresses for constants are set correctly now
Generator initialized with symbol table for auxiliary addresses correctly now
Renamed accumulatorEmpty and corrected "loadToAccumulator(..)"

accumulatorEmpty actually represents whether the accumulator
currently holds the item at the top of the stack.
Its name led to confusion at some points, though, so it is renamed
to accumulatorFreeFromStackTop (this long name is mostly to be able to
remain the boolean meaning)
Address stack is now handled correctly.

Fixed a bug that changed fix addresses because of call-by-reference.
If the top of the stack is currently in the accumulator, its address is
not set to 0 anymore, but only 'accumulatorFreeFromStack = false' is
set.

Instead of directly pushing to the stack a new method
'pushToAddressStack(..)' is used that sets accumulatorFreeFromStack to
true, in addition.

These two changes fix problems the generator had because of the address
stack.