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".
By default now only the first letter is case-sensitive. It is still
possible to choose full or no case-sensitivity as well.
Task-number: QTCREATORBUG-236
Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com>
They should always use the function parameter tooltip.
This fixes a bug where you were offered completion for
C foo( -> C foo(int x)
if C had a constructor taking int x.
Reviewed-by: Thorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>
You now get the function parameters as a completion suggestion when
declaring or defining a function. The tooltip for function calls
is unchanged.
Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
(cherry picked from commit 202fef42ca)
You now get the function parameters as a completion suggestion when
declaring or defining a function. The tooltip for function calls
is unchanged.
Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
Now it shows immediately when there is only a single signature of a
given method/constructor.
(cherry picked from commit 8b9dd766c8)
Conflicts:
src/plugins/cpptools/cppcodecompletion.cpp
Deals with cases like "QString s(", but for the moment doesn't handle
yet "QString const s(".
Done with Roberto Raggi.
(cherry picked from commit fca3ec1f32)
