call of overloaded ‘QString(int)’ is ambiguous

This reverts commit 2a59d2ae.

This reverts commit f4163b8b.

Because apparently, while designing the Objective-C language, somebody
thought it was a world-class idea to allow any white-space between the
'@' character and the subsequent keyword. With this fix, we now
correctly parse:
    @  dynamic
and:
    @
      selector
and:
    @"foo"
     "bar"
    @"mooze"
(This last one is 1 single string split over multiple lines.)
Wonderful, isn't it?

What we (and Clang) do not support, but what GCC supports is something
like:
   @"foo"@@  "bar"  @"mooze"  @@
which is equivalent to @"foobarmooze".

Task-number: QTCREATORBUG-643
Merge-request: 109
Reviewed-by: Thorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>

doing it in 1.3 as well to avoid possible later conflicts

 * Remove duplicate headers.
 * Move own headers to the top.

Reviewed-by: Roberto Raggi

Wasn't using a space to separate the closing angular brackets.

Task-number: QTCREATORBUG-547
Reviewed-by: Thorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>

Task-number: QTCREATORBUG-534
Reviewed-by: Thorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>

- unsigned* was printed as unsigned
- Type **name was printed as Type**name

In preparation for finding macro uses.

* Macro: add offset and length
* MacroUse: add line
* Document: add convenience functions for finding a macro definition, use
  or undefined use at a given location.

Reviewed-by: Erik Verbruggen

Task-number: QTCREATORBUG-384
Reviewed-by: Thorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>

For example std::string, which is a typedef of std::basic_string.

Reviewed-by: Thorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>

Several special cases that are handled by the CPPEditor did not take
into account code that was using tab characters.

Task-number: QTCREATORBUG-292
Reviewed-by: Roberto Raggi