feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity
Files
dc8da57e6452ce4dbd97b1a53de8c297bd4e5bcf
qt-creator/src/libs/3rdparty/cplusplus/AST.cpp

4669 lines
114 KiB
C++
Raw Normal View History

Initial import
2008-12-02 12:01:29 +01:00
// Copyright (c) 2008 Roberto Raggi <roberto.raggi@gmail.com>
//
// Permission is hereby granted, free of charge, to any person obtaining a copy
// of this software and associated documentation files (the "Software"), to deal
// in the Software without restriction, including without limitation the rights
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
// copies of the Software, and to permit persons to whom the Software is
// furnished to do so, subject to the following conditions:
//
// The above copyright notice and this permission notice shall be included in
// all copies or substantial portions of the Software.
//
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
// THE SOFTWARE.
#include "AST.h"
#include "ASTVisitor.h"
Initial work on the pattern matcher for AST nodes.
2009-11-12 17:35:48 +01:00
#include "ASTMatcher.h"
Initial import
2008-12-02 12:01:29 +01:00
#include "MemoryPool.h"
C++: Use soft asserts instead of assert() Some qmake versions ignore "DEFINES += NDEBUG" on Windows. Change-Id: Ibdf3b1036c2331dcef61dcd278463c02754044d2 Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>
2013-05-13 10:20:00 +02:00
#include "cppassert.h"
Initial import
2008-12-02 12:01:29 +01:00
#include <algorithm>
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/*
Rename "[Mm]ethod(s)" to "[Ff]unction(s)" Only methods as programming functions are affected. Besides renaming some actions like "Switch Between Function Declaration/Definition" this mostly touches (api) code comments. This is a follow-up patch to commit 872bfb7. Change-Id: Icb65e8d73b59a022f8885b14df497169543a3b92 Reviewed-by: hjk <hjk121@nokiamail.com>
2013-10-07 13:34:40 +02:00
All firstToken/lastToken functions below which have a doxygen comment with
C++: Clean up dev tools. * Add -h and -help options describing the tools and their usage. * Make the tools compile and run on Windows (MinGW, MSVC). * Rename project dirs, executables and main source files to more meaningful names: - Use same base name for project dir, *.pro file, main source file and (if applicable) script file. - Use the prefix "cplusplus-". - The names are now: - gen-cpp-ast/generate-ast --> cplusplus-update-frontend - mkvisitor --> cplusplus-mkvisitor - cplusplus-dump/cplusplus0 --> cplusplus-ast2png * Get rid of 'c++' shell scripts. * Get rid of duplicates of 'conf.c++'. Rename to 'pp-configuration.inc'. * Introduce src/tools/cplusplus-tools-utils containing common stuff that is used at least in two tools. 'pp-configuration.inc' can also be found here. * cplusplus-update-frontend: - Print file paths of written files to stdout. - Convenience: Use default values referencing the appropriate dirs and files. * cplusplus-mkvisitor: - Take only one argument, namely the path to AST.h. - Convenience: Use default path to AST.h. * cplusplus-ast2png: - Make it run without LD_LIBRARY_PATH. - As the name suggests, generate image files in png format (needs 'dot' from graphviz). - Convenience: Read from stdin, which useful for small snippets. Change-Id: I79c4061fce4a1571c0588dfedd50d4a70715d9df Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>
2012-10-29 13:54:33 +01:00
\generated in it, will be re-generated when the tool "cplusplus-update-frontend" is run.
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
Rename "[Mm]ethod(s)" to "[Ff]unction(s)" Only methods as programming functions are affected. Besides renaming some actions like "Switch Between Function Declaration/Definition" this mostly touches (api) code comments. This is a follow-up patch to commit 872bfb7. Change-Id: Icb65e8d73b59a022f8885b14df497169543a3b92 Reviewed-by: hjk <hjk121@nokiamail.com>
2013-10-07 13:34:40 +02:00
For functions which are hand-coded, or which should not be changed, make sure that
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
the comment is gone.
*/
Cleanup the C++ front-end. Removed CPLUSPLUS_BEGIN/END_NAMESPACE & co and made it possible to compile the parser with CPLUSPLUS_WITHOUT_QT.
2009-10-20 11:21:25 +02:00
using namespace CPlusPlus;
Initial import
2008-12-02 12:01:29 +01:00
AST::AST()
{ }
AST::~AST()
C++: Use soft asserts instead of assert() Some qmake versions ignore "DEFINES += NDEBUG" on Windows. Change-Id: Ibdf3b1036c2331dcef61dcd278463c02754044d2 Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>
2013-05-13 10:20:00 +02:00
{ CPP_CHECK(0); }
Initial import
2008-12-02 12:01:29 +01:00
void AST::accept(ASTVisitor *visitor)
{
if (visitor->preVisit(this))
accept0(visitor);
visitor->postVisit(this);
}
Initial work on the pattern matcher for AST nodes.
2009-11-12 17:35:48 +01:00
bool AST::match(AST *ast, AST *pattern, ASTMatcher *matcher)
{
if (ast == pattern)
return true;
else if (! ast || ! pattern)
return false;
return ast->match(pattern, matcher);
}
bool AST::match(AST *pattern, ASTMatcher *matcher)
{
return match0(pattern, matcher);
}
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int GnuAttributeSpecifierAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
return attribute_token;
}
C++: fix built-in code model to work with shared_ptr on MSVC 2017 These changes target Find Usages feature to work with shared_ptr. Improve libs/3rdparty/cplusplus and plugins/cplusplus: parse __declspec() attribute, call to variadic function template without specified template arguments, if constexpr, c++11 attributes [[value]], function templates with default parameters, resolve order for function vs template with default parameter, template operator->() with default arguments, template specialization with numeric values, find best partial specialization, fix partial specialization for non-first specialized argument Fixes: QTCREATORBUG-7866 Fixes: QTCREATORBUG-20781 Fixes: QTCREATORBUG-22857 Fixes: QTCREATORBUG-17825 Change-Id: I31a080f7729edfb2ee9650f1aff48daeba5a673b Reviewed-by: Christian Kandeler <christian.kandeler@qt.io> Reviewed-by: Nikolai Kosjar <pinaceae.pinus@gmail.com>
2020-05-14 23:07:05 +03:00
int MsvcDeclspecSpecifierAST::firstToken() const
{
return attribute_token;
}
int StdAttributeSpecifierAST::firstToken() const
{
return first_lbracket_token;
}
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BaseSpecifierAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (virtual_token && access_specifier_token)
return std::min(virtual_token, access_specifier_token);
if (virtual_token)
return virtual_token;
if (access_specifier_token)
return access_specifier_token;
Fixed possible crash when asking for the firstToken of an incomplete base class specifier.
2010-07-05 17:07:49 +02:00
if (name)
C++: Fix BaseSpecifierAST::firstToken return Change-Id: I105d94f543d22319571320cd88f791278aac3239 Reviewed-on: http://codereview.qt.nokia.com/2734 Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com> Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2011-08-08 09:54:06 +02:00
return name->firstToken();
Fixed possible crash when asking for the firstToken of an incomplete base class specifier.
2010-07-05 17:07:49 +02:00
// assert?
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BaseSpecifierAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
C++: Support ellipsis on variadic inheritance parsing Change-Id: I571aefdb1f2aba88ba0c7710f16b6d8ad2e8f5a8 Reviewed-by: André Hartmann <aha_1980@gmx.de> Reviewed-by: Orgad Shaneh <orgads@gmail.com> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
2015-02-25 21:22:16 +01:00
if (ellipsis_token)
return ellipsis_token;
else if (name)
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return name->lastToken();
else if (virtual_token && access_specifier_token)
return std::max(virtual_token, access_specifier_token) + 1;
else if (virtual_token)
return virtual_token + 1;
else if (access_specifier_token)
return access_specifier_token + 1;
// assert?
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int AccessDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (access_specifier_token)
return access_specifier_token;
if (slots_token)
return slots_token;
if (colon_token)
return colon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int AccessDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (colon_token)
return colon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (slots_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return slots_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (access_specifier_token)
return access_specifier_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added parser support for Q_INTERFACES.
2010-03-16 17:29:40 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ArrayAccessAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Get rid of PostfixExpressionAST and store the base expression together with the PostfixAST nodes.
2010-06-23 14:38:41 +02:00
if (base_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = base_expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lbracket_token)
return lbracket_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rbracket_token)
return rbracket_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ArrayAccessAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (rbracket_token)
return rbracket_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Get rid of PostfixExpressionAST and store the base expression together with the PostfixAST nodes.
2010-06-23 14:38:41 +02:00
if (lbracket_token)
return lbracket_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (base_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = base_expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ArrayDeclaratorAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lbracket_token)
return lbracket_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rbracket_token)
return rbracket_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ArrayDeclaratorAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (rbracket_token)
return rbracket_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lbracket_token)
return lbracket_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ArrayInitializerAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lbrace_token)
return lbrace_token;
if (expression_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rbrace_token)
return rbrace_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ArrayInitializerAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (rbrace_token)
return rbrace_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lbrace_token)
return lbrace_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int AsmDefinitionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (asm_token)
return asm_token;
if (volatile_token)
return volatile_token;
if (lparen_token)
return lparen_token;
if (rparen_token)
return rparen_token;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int AsmDefinitionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (semicolon_token)
return semicolon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lparen_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (volatile_token)
Fixes: Parsing of GCC asm definitions.
2009-02-05 11:37:51 +01:00
return volatile_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (asm_token)
return asm_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int GnuAttributeAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (identifier_token)
return identifier_token;
if (lparen_token)
return lparen_token;
if (tag_token)
return tag_token;
if (expression_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (rparen_token)
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return rparen_token;
return 0;
Inital support for Q_D/Q_Q declarations.
2009-11-30 16:30:21 +01:00
}
Initial import
2008-12-02 12:01:29 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int GnuAttributeAST::lastToken() const
Inital support for Q_D/Q_Q declarations.
2009-11-30 16:30:21 +01:00
{
if (rparen_token)
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (tag_token)
return tag_token + 1;
if (lparen_token)
Inital support for Q_D/Q_Q declarations.
2009-11-30 16:30:21 +01:00
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (identifier_token)
return identifier_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Inital support for Q_D/Q_Q declarations.
2009-11-30 16:30:21 +01:00
}
Initial import
2008-12-02 12:01:29 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BinaryExpressionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (left_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = left_expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (binary_op_token)
return binary_op_token;
if (right_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = right_expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BinaryExpressionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (right_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = right_expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (binary_op_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return binary_op_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (left_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = left_expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BoolLiteralAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (literal_token)
return literal_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BoolLiteralAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (literal_token)
return literal_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added AST nodes for compound expressions (a GNU extension).
2010-02-04 14:55:18 +01:00
}
Added support for C99 compound literals.
2009-01-13 14:58:29 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BracedInitializerAST::firstToken() const
Added support for C99 compound literals.
2009-01-13 14:58:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lbrace_token)
return lbrace_token;
if (expression_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (comma_token)
return comma_token;
if (rbrace_token)
return rbrace_token;
return 0;
Added support for C99 compound literals.
2009-01-13 14:58:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BracedInitializerAST::lastToken() const
Added support for C99 compound literals.
2009-01-13 14:58:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rbrace_token)
return rbrace_token + 1;
if (comma_token)
return comma_token + 1;
if (expression_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lbrace_token)
return lbrace_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added support for C99 compound literals.
2009-01-13 14:58:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BreakStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (break_token)
return break_token;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BreakStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (semicolon_token)
return semicolon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (break_token)
return break_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CallAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Get rid of PostfixExpressionAST and store the base expression together with the PostfixAST nodes.
2010-06-23 14:38:41 +02:00
if (base_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = base_expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token;
if (expression_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CallAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (rparen_token)
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Get rid of PostfixExpressionAST and store the base expression together with the PostfixAST nodes.
2010-06-23 14:38:41 +02:00
if (lparen_token)
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (base_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = base_expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
Get rid of PostfixExpressionAST and store the base expression together with the PostfixAST nodes.
2010-06-23 14:38:41 +02:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CaptureAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
C++: Store lambda captures in the code model. Done-with: Erik Verbruggen Task-number: QTCREATORBUG-7968 Task-number: QTCREATORBUG-7949 Change-Id: I0cf727052d0a3536ed96ee894b18768c9538c213 Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>
2012-10-25 16:22:42 +02:00
if (amper_token)
return amper_token;
if (identifier)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = identifier->firstToken())
C++: Store lambda captures in the code model. Done-with: Erik Verbruggen Task-number: QTCREATORBUG-7968 Task-number: QTCREATORBUG-7949 Change-Id: I0cf727052d0a3536ed96ee894b18768c9538c213 Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>
2012-10-25 16:22:42 +02:00
return candidate;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CaptureAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
C++: Store lambda captures in the code model. Done-with: Erik Verbruggen Task-number: QTCREATORBUG-7968 Task-number: QTCREATORBUG-7949 Change-Id: I0cf727052d0a3536ed96ee894b18768c9538c213 Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>
2012-10-25 16:22:42 +02:00
if (identifier)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = identifier->lastToken())
C++: Store lambda captures in the code model. Done-with: Erik Verbruggen Task-number: QTCREATORBUG-7968 Task-number: QTCREATORBUG-7949 Change-Id: I0cf727052d0a3536ed96ee894b18768c9538c213 Reviewed-by: Erik Verbruggen <erik.verbruggen@digia.com>
2012-10-25 16:22:42 +02:00
return candidate;
if (amper_token)
return amper_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
Initial import
2008-12-02 12:01:29 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CaseStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (case_token)
return case_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (colon_token)
return colon_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CaseStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (colon_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return colon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (case_token)
return case_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CastExpressionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lparen_token)
return lparen_token;
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CastExpressionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CatchClauseAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (catch_token)
return catch_token;
if (lparen_token)
return lparen_token;
if (exception_declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = exception_declaration->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CatchClauseAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return rparen_token + 1;
Some cleanup in the AST nodes.
2009-06-17 16:08:01 +02:00
if (exception_declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = exception_declaration->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (lparen_token)
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (catch_token)
return catch_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ClassSpecifierAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (classkey_token)
return classkey_token;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Added support for override/final and enum classes Change-Id: I6dfe9dd606781046ff5a1ed61315741d2f332cb8 Reviewed-by: Christian Kamm <christian.d.kamm@nokia.com>
2012-06-25 23:49:17 +04:00
if (final_token)
return final_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (colon_token)
return colon_token;
if (base_clause_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = base_clause_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (dot_dot_dot_token)
return dot_dot_dot_token;
if (lbrace_token)
return lbrace_token;
if (member_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = member_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rbrace_token)
return rbrace_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ClassSpecifierAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (rbrace_token)
return rbrace_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (member_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = member_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lbrace_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return lbrace_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (dot_dot_dot_token)
Parse C++0x base-specifier-list.
2010-03-23 13:52:24 +01:00
return dot_dot_dot_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (base_clause_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = base_clause_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Fixed ClassSpecifierAST::lastToken() to return a valid token.
2010-06-01 11:42:49 +02:00
if (colon_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return colon_token + 1;
Added support for override/final and enum classes Change-Id: I6dfe9dd606781046ff5a1ed61315741d2f332cb8 Reviewed-by: Christian Kamm <christian.d.kamm@nokia.com>
2012-06-25 23:49:17 +04:00
if (final_token)
return final_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (classkey_token)
return classkey_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CompoundExpressionAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (lparen_token)
return lparen_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CompoundExpressionAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (rparen_token)
return rparen_token + 1;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CompoundLiteralAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (lparen_token)
return lparen_token;
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
}
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CompoundLiteralAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token + 1;
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CompoundStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lbrace_token)
return lbrace_token;
if (statement_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rbrace_token)
return rbrace_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CompoundStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (rbrace_token)
return rbrace_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (statement_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lbrace_token)
return lbrace_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ConditionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Fixed the AST field names.
2009-11-10 16:47:16 +01:00
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ConditionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ConditionalExpressionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (condition)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = condition->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (question_token)
return question_token;
if (left_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = left_expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (colon_token)
return colon_token;
if (right_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = right_expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ConditionalExpressionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (right_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = right_expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (colon_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return colon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (left_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = left_expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (question_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return question_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (condition)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = condition->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ContinueStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (continue_token)
return continue_token;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ContinueStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (semicolon_token)
return semicolon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (continue_token)
return continue_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ConversionFunctionIdAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (operator_token)
return operator_token;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (ptr_operator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = ptr_operator_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ConversionFunctionIdAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Fixed the AST field names.
2009-11-10 16:47:16 +01:00
if (ptr_operator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = ptr_operator_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (operator_token)
return operator_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CppCastExpressionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (cast_token)
return cast_token;
if (less_token)
return less_token;
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (greater_token)
return greater_token;
if (lparen_token)
return lparen_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CppCastExpressionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
if (rparen_token)
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (greater_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return greater_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (less_token)
Initial work on *AST::lastToken().
2009-01-02 17:36:08 +01:00
return less_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (cast_token)
return cast_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CtorInitializerAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (colon_token)
return colon_token;
if (member_initializer_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = member_initializer_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (dot_dot_dot_token)
return dot_dot_dot_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int CtorInitializerAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Parse C++0x mem-initializer-list.
2010-03-23 13:43:18 +01:00
if (dot_dot_dot_token)
return dot_dot_dot_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (member_initializer_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = member_initializer_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (colon_token)
return colon_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DeclarationStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Initial import
2008-12-02 12:01:29 +01:00
return 0;
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DeclarationStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DeclaratorAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (ptr_operator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = ptr_operator_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (core_declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = core_declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (postfix_declarator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = postfix_declarator_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (post_attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = post_attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Renamed DeclaratorAST::equals_token
2010-08-16 11:38:34 +02:00
if (equal_token)
return equal_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DeclaratorAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Renamed DeclaratorAST::equals_token
2010-08-16 11:38:34 +02:00
if (equal_token)
return equal_token + 1;
CPlusPlus: Support requires clause in parser Change-Id: Ice6a7a287453516a1cfc296e2c9f16160b3ea130 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: <github-actions-qt-creator@cristianadam.eu> Reviewed-by: Christian Stenger <christian.stenger@qt.io>
2023-02-28 11:09:50 +01:00
if (requiresClause)
return requiresClause->lastToken();
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (post_attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = post_attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (postfix_declarator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = postfix_declarator_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (core_declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = core_declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (ptr_operator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = ptr_operator_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DeclaratorIdAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Accepts `...' when parsing declarator-ids in C++0x.
2010-03-25 10:26:33 +01:00
if (dot_dot_dot_token)
return dot_dot_dot_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DeclaratorIdAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Accepts `...' when parsing declarator-ids in C++0x.
2010-03-25 10:26:33 +01:00
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (dot_dot_dot_token)
Accepts `...' when parsing declarator-ids in C++0x.
2010-03-25 10:26:33 +01:00
return dot_dot_dot_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DeleteExpressionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (scope_token)
return scope_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (delete_token)
return delete_token;
if (lbracket_token)
return lbracket_token;
if (rbracket_token)
return rbracket_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DeleteExpressionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rbracket_token)
Initial import
2008-12-02 12:01:29 +01:00
return rbracket_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lbracket_token)
Implemented DeleteExpressionAST::lastToken().
2009-01-02 17:48:31 +01:00
return lbracket_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (delete_token)
Implemented DeleteExpressionAST::lastToken().
2009-01-02 17:48:31 +01:00
return delete_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (scope_token)
return scope_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DestructorNameAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (tilde_token)
return tilde_token;
C++: handle destructor names with template parameters. Change-Id: I74b4fd5e043db935abc18345b303d294b71e8fc2 Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com> Reviewed-by: Erik Verbruggen <erik.verbruggen@nokia.com>
2012-02-16 10:54:44 +01:00
if (unqualified_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = unqualified_name->firstToken())
C++: handle destructor names with template parameters. Change-Id: I74b4fd5e043db935abc18345b303d294b71e8fc2 Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com> Reviewed-by: Erik Verbruggen <erik.verbruggen@nokia.com>
2012-02-16 10:54:44 +01:00
return candidate;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DestructorNameAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
C++: handle destructor names with template parameters. Change-Id: I74b4fd5e043db935abc18345b303d294b71e8fc2 Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com> Reviewed-by: Erik Verbruggen <erik.verbruggen@nokia.com>
2012-02-16 10:54:44 +01:00
if (unqualified_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = unqualified_name->lastToken())
C++: handle destructor names with template parameters. Change-Id: I74b4fd5e043db935abc18345b303d294b71e8fc2 Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com> Reviewed-by: Erik Verbruggen <erik.verbruggen@nokia.com>
2012-02-16 10:54:44 +01:00
return candidate;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (tilde_token)
return tilde_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DoStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (do_token)
return do_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (while_token)
return while_token;
if (lparen_token)
return lparen_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DoStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Implemented DoStatementAST::lastToken().
2009-01-02 17:51:48 +01:00
if (semicolon_token)
return semicolon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
Implemented DoStatementAST::lastToken().
2009-01-02 17:51:48 +01:00
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
Implemented DoStatementAST::lastToken().
2009-01-02 17:51:48 +01:00
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (while_token)
Implemented DoStatementAST::lastToken().
2009-01-02 17:51:48 +01:00
return while_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (do_token)
return do_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ElaboratedTypeSpecifierAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (classkey_token)
return classkey_token;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ElaboratedTypeSpecifierAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Added attributes to the elaborate-type-specifier AST node.
2010-03-22 18:23:17 +01:00
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (classkey_token)
return classkey_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int EmptyDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int EmptyDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (semicolon_token)
return semicolon_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int EnumSpecifierAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (enum_token)
return enum_token;
C++11: Make 'enum struct', enum-base and opaque enum decls work. For declarations like: enum struct Foo : long int; Change-Id: Id813efdbc31c8d70a4b40bb0101dc33a8dd2556a Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 11:17:29 +02:00
if (key_token)
return key_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++11: Make 'enum struct', enum-base and opaque enum decls work. For declarations like: enum struct Foo : long int; Change-Id: Id813efdbc31c8d70a4b40bb0101dc33a8dd2556a Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 11:17:29 +02:00
if (colon_token)
return colon_token;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
C++11: Make 'enum struct', enum-base and opaque enum decls work. For declarations like: enum struct Foo : long int; Change-Id: Id813efdbc31c8d70a4b40bb0101dc33a8dd2556a Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 11:17:29 +02:00
return candidate;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lbrace_token)
return lbrace_token;
if (enumerator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = enumerator_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Added semantic checks for stray semicolons and topldevel empty declarations.
2010-12-16 12:25:51 +01:00
if (stray_comma_token)
return stray_comma_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rbrace_token)
return rbrace_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int EnumSpecifierAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Implemented EnumSpecifierAST::lastToken().
2009-01-02 17:54:01 +01:00
if (rbrace_token)
return rbrace_token + 1;
Added semantic checks for stray semicolons and topldevel empty declarations.
2010-12-16 12:25:51 +01:00
if (stray_comma_token)
return stray_comma_token + 1;
Fixed the AST field names.
2009-11-10 16:47:16 +01:00
if (enumerator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = enumerator_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Implemented EnumSpecifierAST::lastToken().
2009-01-02 17:54:01 +01:00
if (lbrace_token)
return lbrace_token + 1;
C++11: Make 'enum struct', enum-base and opaque enum decls work. For declarations like: enum struct Foo : long int; Change-Id: Id813efdbc31c8d70a4b40bb0101dc33a8dd2556a Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 11:17:29 +02:00
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
C++11: Make 'enum struct', enum-base and opaque enum decls work. For declarations like: enum struct Foo : long int; Change-Id: Id813efdbc31c8d70a4b40bb0101dc33a8dd2556a Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 11:17:29 +02:00
return candidate;
if (colon_token)
return colon_token + 1;
Implemented EnumSpecifierAST::lastToken().
2009-01-02 17:54:01 +01:00
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++11: Make 'enum struct', enum-base and opaque enum decls work. For declarations like: enum struct Foo : long int; Change-Id: Id813efdbc31c8d70a4b40bb0101dc33a8dd2556a Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 11:17:29 +02:00
if (key_token)
return key_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (enum_token)
return enum_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int EnumeratorAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (identifier_token)
return identifier_token;
if (equal_token)
return equal_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int EnumeratorAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (equal_token)
Initial import
2008-12-02 12:01:29 +01:00
return equal_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (identifier_token)
return identifier_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ExceptionDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Fixed the AST field names.
2009-11-10 16:47:16 +01:00
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Implemented ExceptionDeclarationAST::lastToken().
2009-01-02 17:57:28 +01:00
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (dot_dot_dot_token)
return dot_dot_dot_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ExceptionDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (dot_dot_dot_token)
return dot_dot_dot_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DynamicExceptionSpecificationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (throw_token)
return throw_token;
if (lparen_token)
return lparen_token;
if (dot_dot_dot_token)
return dot_dot_dot_token;
if (type_id_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DynamicExceptionSpecificationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Implemented ExceptionSpecificationAST::lastToken().
2009-01-02 17:59:27 +01:00
if (rparen_token)
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_id_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (dot_dot_dot_token)
Implemented ExceptionSpecificationAST::lastToken().
2009-01-02 17:59:27 +01:00
return dot_dot_dot_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lparen_token)
Implemented ExceptionSpecificationAST::lastToken().
2009-01-02 17:59:27 +01:00
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (throw_token)
return throw_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ExpressionOrDeclarationStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ExpressionOrDeclarationStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ExpressionStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ExpressionStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Implemented ForStatementAST::lastToken().
2009-01-05 10:18:16 +01:00
if (semicolon_token)
return semicolon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ForStatementAST::firstToken() const
Introduced ForeachStatementAST and the bits to parse foreach statements when qtMocRun is enabled.
2009-07-03 09:11:52 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (for_token)
return for_token;
if (lparen_token)
return lparen_token;
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (condition)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = condition->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Introduced ForeachStatementAST and the bits to parse foreach statements when qtMocRun is enabled.
2009-07-03 09:11:52 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ForStatementAST::lastToken() const
Introduced ForeachStatementAST and the bits to parse foreach statements when qtMocRun is enabled.
2009-07-03 09:11:52 +02:00
{
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
Introduced ForeachStatementAST and the bits to parse foreach statements when qtMocRun is enabled.
2009-07-03 09:11:52 +02:00
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token + 1;
if (condition)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = condition->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (for_token)
return for_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Introduced ForeachStatementAST and the bits to parse foreach statements when qtMocRun is enabled.
2009-07-03 09:11:52 +02:00
}
Initial import
2008-12-02 12:01:29 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ForeachStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (foreach_token)
return foreach_token;
if (lparen_token)
return lparen_token;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (comma_token)
return comma_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ForeachStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
Implemented ForStatementAST::lastToken().
2009-01-05 10:18:16 +01:00
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (comma_token)
return comma_token + 1;
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
Implemented ForStatementAST::lastToken().
2009-01-05 10:18:16 +01:00
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (foreach_token)
return foreach_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int FunctionDeclaratorAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lparen_token)
return lparen_token;
Some cleanup in the C++ AST.
2010-08-26 15:55:31 +02:00
if (parameter_declaration_clause)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = parameter_declaration_clause->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
CppEditor: Fix "move function definition" ... for member functions with exception specification and/or reference qualifiers. The FunctionDeclaratorAST::cv_qualifier_list member can contain both the proper qualifiers "const" and "volatile" as well as the pseudo-qualifiers "override" and "final". The problem is that the former appear before exception specification and reference qualifiers, whereas the latter come afterwards. Therefore, when calculating the declarator's first and last tokens, we can't just mechanically check the different declarator members in order. Instead, we need to compare the token values to see which comes first. Task-number: QTCREATORBUG-27132 Change-Id: I924f9afe49453fa51b4a2fe010d1cc00c9defad1 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: <github-actions-qt-creator@cristianadam.eu> Reviewed-by: Christian Stenger <christian.stenger@qt.io>
2022-04-04 18:05:31 +02:00
const int firstQualListToken = cv_qualifier_list ? cv_qualifier_list->firstToken() : 0;
const auto isBeforeFirstQualListToken = [firstQualListToken](int token) {
return token && (!firstQualListToken || token < firstQualListToken);
};
if (isBeforeFirstQualListToken(ref_qualifier_token))
C++11: Accept ref-qualifiers in function declarators. Means void foo() const &; void bar() &&; and the corresponding pointer-to-member declarators now parse. Change-Id: Idbf295bd4f51cd5d9e38efcac1940b8cc2e32fce Reviewed-by: hjk <qthjk@ovi.com>
2012-09-17 12:26:49 +02:00
return ref_qualifier_token;
CppEditor: Fix "move function definition" ... for member functions with exception specification and/or reference qualifiers. The FunctionDeclaratorAST::cv_qualifier_list member can contain both the proper qualifiers "const" and "volatile" as well as the pseudo-qualifiers "override" and "final". The problem is that the former appear before exception specification and reference qualifiers, whereas the latter come afterwards. Therefore, when calculating the declarator's first and last tokens, we can't just mechanically check the different declarator members in order. Instead, we need to compare the token values to see which comes first. Task-number: QTCREATORBUG-27132 Change-Id: I924f9afe49453fa51b4a2fe010d1cc00c9defad1 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: <github-actions-qt-creator@cristianadam.eu> Reviewed-by: Christian Stenger <christian.stenger@qt.io>
2022-04-04 18:05:31 +02:00
if (exception_specification) {
const int candidate = exception_specification->firstToken();
if (isBeforeFirstQualListToken(candidate))
return candidate;
}
if (trailing_return_type) {
const int candidate = trailing_return_type->firstToken();
if (isBeforeFirstQualListToken(candidate))
return candidate;
}
if (firstQualListToken)
return firstQualListToken;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (as_cpp_initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = as_cpp_initializer->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int FunctionDeclaratorAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (as_cpp_initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = as_cpp_initializer->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
CppEditor: Fix "move function definition" ... for member functions with exception specification and/or reference qualifiers. The FunctionDeclaratorAST::cv_qualifier_list member can contain both the proper qualifiers "const" and "volatile" as well as the pseudo-qualifiers "override" and "final". The problem is that the former appear before exception specification and reference qualifiers, whereas the latter come afterwards. Therefore, when calculating the declarator's first and last tokens, we can't just mechanically check the different declarator members in order. Instead, we need to compare the token values to see which comes first. Task-number: QTCREATORBUG-27132 Change-Id: I924f9afe49453fa51b4a2fe010d1cc00c9defad1 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: <github-actions-qt-creator@cristianadam.eu> Reviewed-by: Christian Stenger <christian.stenger@qt.io>
2022-04-04 18:05:31 +02:00
const int lastQualListToken = cv_qualifier_list ? cv_qualifier_list->lastToken() : 0;
const auto tokenOrLastQualListToken = [lastQualListToken](int token) {
return std::max(token ? token + 1 : 0, lastQualListToken);
};
const auto tokenFromAstOrLastQualListToken = [lastQualListToken](const AST *ast) {
return std::max(ast ? ast->lastToken() : 0, lastQualListToken);
};
if (int candidate = tokenFromAstOrLastQualListToken(trailing_return_type))
return candidate;
if (int candidate = tokenFromAstOrLastQualListToken(exception_specification))
return candidate;
if (int candidate = tokenOrLastQualListToken(ref_qualifier_token))
return candidate;
if (lastQualListToken)
return lastQualListToken;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
Implemented FunctionDeclaratorAST::lastToken().
2009-01-05 10:20:58 +01:00
return rparen_token + 1;
Some cleanup in the C++ AST.
2010-08-26 15:55:31 +02:00
if (parameter_declaration_clause)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = parameter_declaration_clause->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int FunctionDefinitionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (qt_invokable_token)
return qt_invokable_token;
Fixed the AST field names.
2009-11-10 16:47:16 +01:00
if (decl_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = decl_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (ctor_initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = ctor_initializer->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (function_body)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = function_body->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int FunctionDefinitionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (function_body)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = function_body->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (ctor_initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = ctor_initializer->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (decl_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = decl_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (qt_invokable_token)
return qt_invokable_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int GotoStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (goto_token)
return goto_token;
if (identifier_token)
return identifier_token;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int GotoStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Implemented GotoStatementAST::lastToken().
2009-01-05 10:24:09 +01:00
if (semicolon_token)
return semicolon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (identifier_token)
Implemented GotoStatementAST::lastToken().
2009-01-05 10:24:09 +01:00
return identifier_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (goto_token)
Implemented GotoStatementAST::lastToken().
2009-01-05 10:24:09 +01:00
return goto_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int IdExpressionAST::firstToken() const
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
{
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return candidate;
Implemented GotoStatementAST::lastToken().
2009-01-05 10:24:09 +01:00
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int IdExpressionAST::lastToken() const
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
{
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return candidate;
return 1;
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int IfStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (if_token)
return if_token;
C++: fix built-in code model to work with shared_ptr on MSVC 2017 These changes target Find Usages feature to work with shared_ptr. Improve libs/3rdparty/cplusplus and plugins/cplusplus: parse __declspec() attribute, call to variadic function template without specified template arguments, if constexpr, c++11 attributes [[value]], function templates with default parameters, resolve order for function vs template with default parameter, template operator->() with default arguments, template specialization with numeric values, find best partial specialization, fix partial specialization for non-first specialized argument Fixes: QTCREATORBUG-7866 Fixes: QTCREATORBUG-20781 Fixes: QTCREATORBUG-22857 Fixes: QTCREATORBUG-17825 Change-Id: I31a080f7729edfb2ee9650f1aff48daeba5a673b Reviewed-by: Christian Kandeler <christian.kandeler@qt.io> Reviewed-by: Nikolai Kosjar <pinaceae.pinus@gmail.com>
2020-05-14 23:07:05 +03:00
if (constexpr_token)
return constexpr_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lparen_token)
return lparen_token;
if (condition)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = condition->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (else_token)
return else_token;
if (else_statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = else_statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int IfStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (else_statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = else_statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (else_token)
Initial import
2008-12-02 12:01:29 +01:00
return else_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
Implemented IfStatementAST::lastToken().
2009-01-05 10:26:20 +01:00
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (condition)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = condition->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
Implemented IfStatementAST::lastToken().
2009-01-05 10:26:20 +01:00
return lparen_token + 1;
C++: fix built-in code model to work with shared_ptr on MSVC 2017 These changes target Find Usages feature to work with shared_ptr. Improve libs/3rdparty/cplusplus and plugins/cplusplus: parse __declspec() attribute, call to variadic function template without specified template arguments, if constexpr, c++11 attributes [[value]], function templates with default parameters, resolve order for function vs template with default parameter, template operator->() with default arguments, template specialization with numeric values, find best partial specialization, fix partial specialization for non-first specialized argument Fixes: QTCREATORBUG-7866 Fixes: QTCREATORBUG-20781 Fixes: QTCREATORBUG-22857 Fixes: QTCREATORBUG-17825 Change-Id: I31a080f7729edfb2ee9650f1aff48daeba5a673b Reviewed-by: Christian Kandeler <christian.kandeler@qt.io> Reviewed-by: Nikolai Kosjar <pinaceae.pinus@gmail.com>
2020-05-14 23:07:05 +03:00
if (constexpr_token)
return constexpr_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (if_token)
return if_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LabeledStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (label_token)
return label_token;
if (colon_token)
return colon_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LabeledStatementAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (colon_token)
Implemented LabeledStatementAST::lastToken().
2009-01-05 10:27:49 +01:00
return colon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (label_token)
return label_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LambdaCaptureAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (default_capture_token)
return default_capture_token;
if (capture_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = capture_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LambdaCaptureAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (capture_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = capture_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (default_capture_token)
return default_capture_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LambdaDeclaratorAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (lparen_token)
return lparen_token;
if (parameter_declaration_clause)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = parameter_declaration_clause->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (attributes)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attributes->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (mutable_token)
return mutable_token;
if (exception_specification)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = exception_specification->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (trailing_return_type)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = trailing_return_type->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LambdaDeclaratorAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (trailing_return_type)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = trailing_return_type->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (exception_specification)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = exception_specification->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (mutable_token)
return mutable_token + 1;
if (attributes)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attributes->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token + 1;
if (parameter_declaration_clause)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = parameter_declaration_clause->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LambdaExpressionAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (lambda_introducer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = lambda_introducer->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lambda_declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = lambda_declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LambdaExpressionAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lambda_declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = lambda_declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lambda_introducer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = lambda_introducer->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LambdaIntroducerAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (lbracket_token)
return lbracket_token;
if (lambda_capture)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = lambda_capture->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rbracket_token)
return rbracket_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LambdaIntroducerAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (rbracket_token)
return rbracket_token + 1;
if (lambda_capture)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = lambda_capture->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lbracket_token)
return lbracket_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
Initial import
2008-12-02 12:01:29 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LinkageBodyAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lbrace_token)
return lbrace_token;
if (declaration_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rbrace_token)
return rbrace_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LinkageBodyAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Implemented LinkageBodyAST::lastToken().
2009-01-05 10:29:12 +01:00
if (rbrace_token)
return rbrace_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (declaration_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lbrace_token)
return lbrace_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LinkageSpecificationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (extern_token)
return extern_token;
if (extern_type_token)
return extern_type_token;
if (declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int LinkageSpecificationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (extern_type_token)
cleanup
2009-06-05 09:44:25 +02:00
return extern_type_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (extern_token)
return extern_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int MemInitializerAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++11: Allow uniform initialization in ctor init lists. So class C { C() : _x{12}, _y({12}) {} }; now parses correctly. Change-Id: I4281dcb0541a86b550e74630cad6ae0a59fef1b4 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-17 09:58:09 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int MemInitializerAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
C++11: Allow uniform initialization in ctor init lists. So class C { C() : _x{12}, _y({12}) {} }; now parses correctly. Change-Id: I4281dcb0541a86b550e74630cad6ae0a59fef1b4 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-17 09:58:09 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int MemberAccessAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Get rid of PostfixExpressionAST and store the base expression together with the PostfixAST nodes.
2010-06-23 14:38:41 +02:00
if (base_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = base_expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (access_token)
return access_token;
if (template_token)
return template_token;
if (member_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = member_name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int MemberAccessAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (member_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = member_name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (template_token)
Implemented MemberAccessAST::lastToken().
2009-01-05 10:32:28 +01:00
return template_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (access_token)
Get rid of PostfixExpressionAST and store the base expression together with the PostfixAST nodes.
2010-06-23 14:38:41 +02:00
return access_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (base_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = base_expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NamedTypeSpecifierAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NamedTypeSpecifierAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NamespaceAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
C++11: handle inline namespaces. Change-Id: Iafdcd5bc72d9724e217767ae9c216be4363cc0d3 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 10:19:58 +01:00
if (inline_token)
return inline_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (namespace_token)
return namespace_token;
if (identifier_token)
return identifier_token;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (linkage_body)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = linkage_body->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NamespaceAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (linkage_body)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = linkage_body->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (identifier_token)
Initial import
2008-12-02 12:01:29 +01:00
return identifier_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (namespace_token)
return namespace_token + 1;
C++11: handle inline namespaces. Change-Id: Iafdcd5bc72d9724e217767ae9c216be4363cc0d3 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 10:19:58 +01:00
if (inline_token)
return inline_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NamespaceAliasDefinitionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (namespace_token)
return namespace_token;
if (namespace_name_token)
return namespace_name_token;
if (equal_token)
return equal_token;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NamespaceAliasDefinitionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Implemented NamespaceAliasDefinitionAST::lastToken().
2009-01-05 10:40:11 +01:00
if (semicolon_token)
return semicolon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (equal_token)
Implemented NamespaceAliasDefinitionAST::lastToken().
2009-01-05 10:40:11 +01:00
return equal_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (namespace_name_token)
cleanup
2009-06-05 09:44:25 +02:00
return namespace_name_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (namespace_token)
return namespace_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NestedDeclaratorAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lparen_token)
return lparen_token;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NestedDeclaratorAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Implemented NestedDeclaratorAST::lastToken().
2009-01-05 10:41:26 +01:00
if (rparen_token)
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NestedExpressionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lparen_token)
return lparen_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NestedExpressionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Implemented NestedExpressionAST::lastToken()
2009-01-05 14:07:57 +01:00
if (rparen_token)
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NestedNameSpecifierAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (class_or_namespace_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = class_or_namespace_name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Implemented NestedExpressionAST::lastToken()
2009-01-05 14:07:57 +01:00
if (scope_token)
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return scope_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NestedNameSpecifierAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (scope_token)
return scope_token + 1;
if (class_or_namespace_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = class_or_namespace_name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Improved the implementation of new-expressions.
2009-02-10 14:43:19 +01:00
}
Accept the next-declarator in NewDeclaratorAST::accept() and implemented NewDeclarator::lastToken().
2009-01-06 12:13:49 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NewArrayDeclaratorAST::firstToken() const
Improved the implementation of new-expressions.
2009-02-10 14:43:19 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lbracket_token)
return lbracket_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rbracket_token)
return rbracket_token;
return 0;
Improved the implementation of new-expressions.
2009-02-10 14:43:19 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NewArrayDeclaratorAST::lastToken() const
Improved the implementation of new-expressions.
2009-02-10 14:43:19 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rbracket_token)
return rbracket_token + 1;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lbracket_token)
return lbracket_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NewExpressionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
if (scope_token)
return scope_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (new_token)
return new_token;
if (new_placement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = new_placement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token;
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (new_type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = new_type_id->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (new_initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = new_initializer->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NewExpressionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (new_initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = new_initializer->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (new_type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = new_type_id->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token + 1;
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (new_placement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = new_placement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Improved the implementation of new-expressions.
2009-02-10 14:43:19 +01:00
if (new_token)
Implemented NewExpressionAST::lastToken() and NewInitializerAST::lastToken().
2009-01-06 11:30:42 +01:00
return new_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (scope_token)
Implemented NewExpressionAST::lastToken() and NewInitializerAST::lastToken().
2009-01-06 11:30:42 +01:00
return scope_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ExpressionListParenAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (lparen_token)
return lparen_token;
if (expression_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ExpressionListParenAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (rparen_token)
return rparen_token + 1;
if (expression_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
Initial import
2008-12-02 12:01:29 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NewTypeIdAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (ptr_operator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = ptr_operator_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (new_array_declarator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = new_array_declarator_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NewTypeIdAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Fixed the AST field names.
2009-11-10 16:47:16 +01:00
if (new_array_declarator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = new_array_declarator_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (ptr_operator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = ptr_operator_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NumericLiteralAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (literal_token)
return literal_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NumericLiteralAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (literal_token)
return literal_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCClassDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (interface_token)
return interface_token;
if (implementation_token)
return implementation_token;
if (class_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = class_name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token;
if (category_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = category_name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (colon_token)
return colon_token;
if (superclass)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = superclass->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (protocol_refs)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = protocol_refs->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (inst_vars_decl)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = inst_vars_decl->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (member_declaration_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = member_declaration_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (end_token)
return end_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCClassDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (end_token)
return end_token + 1;
if (member_declaration_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = member_declaration_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (inst_vars_decl)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = inst_vars_decl->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (protocol_refs)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = protocol_refs->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (superclass)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = superclass->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (colon_token)
return colon_token + 1;
if (rparen_token)
return rparen_token + 1;
if (category_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = category_name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (class_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = class_name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (implementation_token)
return implementation_token + 1;
if (interface_token)
return interface_token + 1;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCClassForwardDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (class_token)
return class_token;
if (identifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = identifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCClassForwardDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (semicolon_token)
return semicolon_token + 1;
if (identifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = identifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (class_token)
return class_token + 1;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCDynamicPropertiesDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (dynamic_token)
return dynamic_token;
if (property_identifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = property_identifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCDynamicPropertiesDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (semicolon_token)
return semicolon_token + 1;
if (property_identifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = property_identifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (dynamic_token)
return dynamic_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCEncodeExpressionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (encode_token)
return encode_token;
if (type_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCEncodeExpressionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (encode_token)
return encode_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCFastEnumerationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (for_token)
return for_token;
if (lparen_token)
return lparen_token;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (in_token)
return in_token;
if (fast_enumeratable_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = fast_enumeratable_expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCFastEnumerationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token + 1;
if (fast_enumeratable_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = fast_enumeratable_expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (in_token)
return in_token + 1;
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (for_token)
return for_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCInstanceVariablesDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lbrace_token)
return lbrace_token;
if (instance_variable_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = instance_variable_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rbrace_token)
return rbrace_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCInstanceVariablesDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rbrace_token)
return rbrace_token + 1;
if (instance_variable_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = instance_variable_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lbrace_token)
return lbrace_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCMessageArgumentAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (parameter_value_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = parameter_value_expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCMessageArgumentAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (parameter_value_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = parameter_value_expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCMessageArgumentDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (param_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = param_name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCMessageArgumentDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (param_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = param_name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCMessageExpressionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lbracket_token)
return lbracket_token;
if (receiver_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = receiver_expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (selector)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = selector->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (argument_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = argument_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rbracket_token)
return rbracket_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCMessageExpressionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rbracket_token)
return rbracket_token + 1;
if (argument_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = argument_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (selector)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = selector->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (receiver_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = receiver_expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lbracket_token)
return lbracket_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCMethodDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (method_prototype)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = method_prototype->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (function_body)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = function_body->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCMethodDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
SimpleDeclarationAST::lastToken().
2009-01-06 11:48:39 +01:00
if (semicolon_token)
return semicolon_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (function_body)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = function_body->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (method_prototype)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = method_prototype->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCMethodPrototypeAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (method_type_token)
return method_type_token;
if (type_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (selector)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = selector->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (argument_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = argument_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (dot_dot_dot_token)
return dot_dot_dot_token;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCMethodPrototypeAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (dot_dot_dot_token)
return dot_dot_dot_token + 1;
if (argument_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = argument_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (selector)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = selector->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (method_type_token)
return method_type_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCPropertyAttributeAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (attribute_identifier_token)
return attribute_identifier_token;
if (equals_token)
return equals_token;
if (method_selector)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = method_selector->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCPropertyAttributeAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (method_selector)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = method_selector->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (equals_token)
return equals_token + 1;
if (attribute_identifier_token)
return attribute_identifier_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCPropertyDeclarationAST::firstToken() const
Simplified ObjC selectors in the AST.
2010-02-23 17:43:40 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (property_token)
return property_token;
if (lparen_token)
return lparen_token;
if (property_attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = property_attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (simple_declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = simple_declaration->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Simplified ObjC selectors in the AST.
2010-02-23 17:43:40 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCPropertyDeclarationAST::lastToken() const
Simplified ObjC selectors in the AST.
2010-02-23 17:43:40 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (simple_declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = simple_declaration->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token + 1;
if (property_attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = property_attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (property_token)
return property_token + 1;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Simplified ObjC selectors in the AST.
2010-02-23 17:43:40 +01:00
}
Initial import
2008-12-02 12:01:29 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCProtocolDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (protocol_token)
return protocol_token;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (protocol_refs)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = protocol_refs->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (member_declaration_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = member_declaration_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (end_token)
return end_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCProtocolDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (end_token)
return end_token + 1;
if (member_declaration_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = member_declaration_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (protocol_refs)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = protocol_refs->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (protocol_token)
return protocol_token + 1;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCProtocolExpressionAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (protocol_token)
return protocol_token;
if (lparen_token)
return lparen_token;
if (identifier_token)
return identifier_token;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCProtocolExpressionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
return rparen_token + 1;
if (identifier_token)
return identifier_token + 1;
if (lparen_token)
return lparen_token + 1;
if (protocol_token)
return protocol_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCProtocolForwardDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (protocol_token)
return protocol_token;
if (identifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = identifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCProtocolForwardDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (semicolon_token)
return semicolon_token + 1;
if (identifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = identifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (protocol_token)
return protocol_token + 1;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
Recognize C++0x sizeof... expressions.
2010-03-25 10:43:16 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCProtocolRefsAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (less_token)
return less_token;
if (identifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = identifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (greater_token)
return greater_token;
return 0;
}
Recognize C++0x sizeof... expressions.
2010-03-25 10:43:16 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCProtocolRefsAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (greater_token)
return greater_token + 1;
if (identifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = identifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (less_token)
return less_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
Recognize C++0x sizeof... expressions.
2010-03-25 10:43:16 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSelectorAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (selector_argument_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = selector_argument_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSelectorAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (selector_argument_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = selector_argument_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
Initial import
2008-12-02 12:01:29 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSelectorArgumentAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (name_token)
return name_token;
if (colon_token)
return colon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSelectorArgumentAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (colon_token)
return colon_token + 1;
if (name_token)
return name_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSelectorExpressionAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (selector_token)
return selector_token;
if (lparen_token)
return lparen_token;
if (selector)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = selector->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
}
Initial import
2008-12-02 12:01:29 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSelectorExpressionAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
return rparen_token + 1;
if (selector)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = selector->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (selector_token)
return selector_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSynchronizedStatementAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (synchronized_token)
return synchronized_token;
if (lparen_token)
return lparen_token;
if (synchronized_object)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = synchronized_object->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
Initial import
2008-12-02 12:01:29 +01:00
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
}
Ported the accept methods.
2009-11-10 16:19:52 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSynchronizedStatementAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
SwitchStatementAST::lastToken().
2009-01-06 11:51:30 +01:00
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (synchronized_object)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = synchronized_object->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
SwitchStatementAST::lastToken().
2009-01-06 11:51:30 +01:00
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (synchronized_token)
return synchronized_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSynthesizedPropertiesDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (synthesized_token)
return synthesized_token;
if (property_identifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = property_identifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSynthesizedPropertiesDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (semicolon_token)
return semicolon_token + 1;
if (property_identifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = property_identifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (synthesized_token)
return synthesized_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSynthesizedPropertyAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (property_identifier_token)
return property_identifier_token;
if (equals_token)
return equals_token;
if (alias_identifier_token)
return alias_identifier_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCSynthesizedPropertyAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (alias_identifier_token)
return alias_identifier_token + 1;
if (equals_token)
return equals_token + 1;
if (property_identifier_token)
return property_identifier_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCTypeNameAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (lparen_token)
return lparen_token;
if (type_qualifier_token)
return type_qualifier_token;
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCTypeNameAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
return rparen_token + 1;
Initial import
2008-12-02 12:01:29 +01:00
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_qualifier_token)
return type_qualifier_token + 1;
if (lparen_token)
return lparen_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCVisibilityDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (visibility_token)
return visibility_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ObjCVisibilityDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (visibility_token)
return visibility_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int OperatorAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (op_token)
return op_token;
if (open_token)
return open_token;
if (close_token)
return close_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int OperatorAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (close_token)
return close_token + 1;
if (open_token)
return open_token + 1;
if (op_token)
return op_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int OperatorFunctionIdAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (operator_token)
return operator_token;
if (op)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = op->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Merge ichecker branch changes into the mainline. New project can be found under src/tools/ICheck
2010-01-19 15:26:08 +10:00
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int OperatorFunctionIdAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (op)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = op->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (operator_token)
return operator_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ParameterDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (equal_token)
return equal_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ParameterDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (equal_token)
return equal_token + 1;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ParameterDeclarationClauseAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (parameter_declaration_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = parameter_declaration_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (dot_dot_dot_token)
return dot_dot_dot_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ParameterDeclarationClauseAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (dot_dot_dot_token)
return dot_dot_dot_token + 1;
if (parameter_declaration_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = parameter_declaration_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int PointerAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (star_token)
return star_token;
if (cv_qualifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = cv_qualifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int PointerAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (cv_qualifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = cv_qualifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (star_token)
return star_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int PointerToMemberAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (global_scope_token)
return global_scope_token;
if (nested_name_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = nested_name_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (star_token)
return star_token;
if (cv_qualifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = cv_qualifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++11: Accept ref-qualifiers in function declarators. Means void foo() const &; void bar() &&; and the corresponding pointer-to-member declarators now parse. Change-Id: Idbf295bd4f51cd5d9e38efcac1940b8cc2e32fce Reviewed-by: hjk <qthjk@ovi.com>
2012-09-17 12:26:49 +02:00
if (ref_qualifier_token)
return ref_qualifier_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int PointerToMemberAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
C++11: Accept ref-qualifiers in function declarators. Means void foo() const &; void bar() &&; and the corresponding pointer-to-member declarators now parse. Change-Id: Idbf295bd4f51cd5d9e38efcac1940b8cc2e32fce Reviewed-by: hjk <qthjk@ovi.com>
2012-09-17 12:26:49 +02:00
if (ref_qualifier_token)
return ref_qualifier_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (cv_qualifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = cv_qualifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (star_token)
return star_token + 1;
if (nested_name_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = nested_name_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (global_scope_token)
return global_scope_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int PostIncrDecrAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (base_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = base_expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (incr_decr_token)
return incr_decr_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int PostIncrDecrAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (incr_decr_token)
return incr_decr_token + 1;
if (base_expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = base_expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtEnumDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (enum_specifier_token)
return enum_specifier_token;
if (lparen_token)
return lparen_token;
if (enumerator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = enumerator_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtEnumDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
return rparen_token + 1;
if (enumerator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = enumerator_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (enum_specifier_token)
return enum_specifier_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtFlagsDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (flags_specifier_token)
return flags_specifier_token;
if (lparen_token)
return lparen_token;
if (flag_enums_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = flag_enums_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtFlagsDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
return rparen_token + 1;
if (flag_enums_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = flag_enums_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (flags_specifier_token)
return flags_specifier_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtInterfaceNameAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (interface_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = interface_name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (constraint_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = constraint_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtInterfaceNameAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (constraint_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = constraint_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (interface_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = interface_name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtInterfacesDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (interfaces_token)
return interfaces_token;
if (lparen_token)
return lparen_token;
if (interface_name_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = interface_name_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtInterfacesDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
return rparen_token + 1;
if (interface_name_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = interface_name_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (interfaces_token)
return interfaces_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtMemberDeclarationAST::firstToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (q_token)
return q_token;
if (lparen_token)
return lparen_token;
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtMemberDeclarationAST::lastToken() const
Initial import
2008-12-02 12:01:29 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
WhileStatementAST::lastToken().
2009-01-06 12:10:39 +01:00
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
WhileStatementAST::lastToken().
2009-01-06 12:10:39 +01:00
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (q_token)
return q_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Initial import
2008-12-02 12:01:29 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtMethodAST::firstToken() const
Parse ObjC @class declarations.
2009-01-08 12:02:07 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (method_token)
return method_token;
if (lparen_token)
return lparen_token;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Parse ObjC @class declarations.
2009-01-08 12:02:07 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtMethodAST::lastToken() const
Parse ObjC @class declarations.
2009-01-08 12:02:07 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
return rparen_token + 1;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (method_token)
return method_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
Parse ObjC @class declarations.
2009-01-08 12:02:07 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtObjectTagAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (q_object_token)
return q_object_token;
return 0;
Parse ObjC @class declarations.
2009-01-08 12:02:07 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtObjectTagAST::lastToken() const
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (q_object_token)
return q_object_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtPrivateSlotAST::firstToken() const
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (q_private_slot_token)
return q_private_slot_token;
if (lparen_token)
return lparen_token;
if (dptr_token)
return dptr_token;
if (dptr_lparen_token)
return dptr_lparen_token;
if (dptr_rparen_token)
return dptr_rparen_token;
if (comma_token)
return comma_token;
Some cleanup in the C++ AST.
2010-08-26 15:55:31 +02:00
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
}
Parse ObjC @class declarations.
2009-01-08 12:02:07 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtPrivateSlotAST::lastToken() const
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
return rparen_token + 1;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Some cleanup in the C++ AST.
2010-08-26 15:55:31 +02:00
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (comma_token)
return comma_token + 1;
if (dptr_rparen_token)
return dptr_rparen_token + 1;
if (dptr_lparen_token)
return dptr_lparen_token + 1;
if (dptr_token)
return dptr_token + 1;
if (lparen_token)
return lparen_token + 1;
if (q_private_slot_token)
return q_private_slot_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtPropertyDeclarationAST::firstToken() const
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (property_specifier_token)
return property_specifier_token;
if (lparen_token)
return lparen_token;
C++: Add parsing of Q_PRIVATE_PROPERTY. Reviewed-by: Roberto Raggi
2010-12-08 15:08:03 +01:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
C++: Add parsing of Q_PRIVATE_PROPERTY. Reviewed-by: Roberto Raggi
2010-12-08 15:08:03 +01:00
return candidate;
if (comma_token)
return comma_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (property_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = property_name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Some cleanup in the C++ AST.
2010-08-26 15:55:31 +02:00
if (property_declaration_item_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = property_declaration_item_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
}
Return valid tokens for the Objc nodes.
2010-06-03 16:38:25 +02:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtPropertyDeclarationAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
Cleaned the ObjC AST up.
2009-08-05 17:14:08 +02:00
if (rparen_token)
return rparen_token + 1;
Some cleanup in the C++ AST.
2010-08-26 15:55:31 +02:00
if (property_declaration_item_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = property_declaration_item_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (property_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = property_name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: Add parsing of Q_PRIVATE_PROPERTY. Reviewed-by: Roberto Raggi
2010-12-08 15:08:03 +01:00
if (comma_token)
return comma_token + 1;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
C++: Add parsing of Q_PRIVATE_PROPERTY. Reviewed-by: Roberto Raggi
2010-12-08 15:08:03 +01:00
return candidate;
Cleaned the ObjC AST up.
2009-08-05 17:14:08 +02:00
if (lparen_token)
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (property_specifier_token)
return property_specifier_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtPropertyDeclarationItemAST::firstToken() const
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (item_name_token)
return item_name_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QtPropertyDeclarationItemAST::lastToken() const
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (item_name_token)
return item_name_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QualifiedNameAST::firstToken() const
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (global_scope_token)
return global_scope_token;
if (nested_name_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = nested_name_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (unqualified_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = unqualified_name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int QualifiedNameAST::lastToken() const
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (unqualified_name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = unqualified_name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (nested_name_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = nested_name_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (global_scope_token)
return global_scope_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ReferenceAST::firstToken() const
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (reference_token)
return reference_token;
return 0;
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ReferenceAST::lastToken() const
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (reference_token)
return reference_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added AST for a bit of ObjC.
2009-07-13 09:45:28 +02:00
}
Parse ObjC @class declarations.
2009-01-08 12:02:07 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ReturnStatementAST::firstToken() const
AST additions for ObjC send_msg.
2009-07-15 12:11:07 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (return_token)
return return_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
Fixed potential 0 pointer deref.
2009-12-18 16:56:31 +01:00
return 0;
AST additions for ObjC send_msg.
2009-07-15 12:11:07 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ReturnStatementAST::lastToken() const
AST additions for ObjC send_msg.
2009-07-15 12:11:07 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (semicolon_token)
return semicolon_token + 1;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (return_token)
return return_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
}
AST additions for ObjC send_msg.
2009-07-15 12:11:07 +02:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int SimpleDeclarationAST::firstToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (qt_invokable_token)
return qt_invokable_token;
if (decl_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = decl_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
Added Semantic checks for ObjC methods.
2009-07-31 16:03:48 +02:00
return 0;
AST additions for ObjC send_msg.
2009-07-15 12:11:07 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int SimpleDeclarationAST::lastToken() const
Added ObjC protocol expressions.
2009-07-16 12:18:05 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (semicolon_token)
return semicolon_token + 1;
if (declarator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (decl_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = decl_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (qt_invokable_token)
return qt_invokable_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added ObjC protocol expressions.
2009-07-16 12:18:05 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int SimpleNameAST::firstToken() const
Added ObjC protocol expressions.
2009-07-16 12:18:05 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (identifier_token)
return identifier_token;
return 0;
}
Added ObjC protocol expressions.
2009-07-16 12:18:05 +02:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int SimpleNameAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
Added ObjC protocol expressions.
2009-07-16 12:18:05 +02:00
if (identifier_token)
return identifier_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added ObjC protocol expressions.
2009-07-16 12:18:05 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int SimpleSpecifierAST::firstToken() const
Added ObjC encode expressions.
2009-07-16 12:44:47 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (specifier_token)
return specifier_token;
return 0;
Added ObjC encode expressions.
2009-07-16 12:44:47 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int SimpleSpecifierAST::lastToken() const
Added ObjC encode expressions.
2009-07-16 12:44:47 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (specifier_token)
return specifier_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added ObjC encode expressions.
2009-07-16 12:44:47 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int SizeofExpressionAST::firstToken() const
Added ObjC encode expressions.
2009-07-16 12:44:47 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (sizeof_token)
return sizeof_token;
if (dot_dot_dot_token)
return dot_dot_dot_token;
if (lparen_token)
return lparen_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Added ObjC encode expressions.
2009-07-16 12:44:47 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int SizeofExpressionAST::lastToken() const
Added ObjC encode expressions.
2009-07-16 12:44:47 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
return rparen_token + 1;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (dot_dot_dot_token)
return dot_dot_dot_token + 1;
if (sizeof_token)
return sizeof_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added ObjC encode expressions.
2009-07-16 12:44:47 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int StringLiteralAST::firstToken() const
Improved ObjC parsing, and added semantic checks.
2009-07-28 16:34:15 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (literal_token)
return literal_token;
if (next)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = next->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Improved ObjC parsing, and added semantic checks.
2009-07-28 16:34:15 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int StringLiteralAST::lastToken() const
Improved ObjC parsing, and added semantic checks.
2009-07-28 16:34:15 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (next)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = next->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (literal_token)
return literal_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Improved ObjC parsing, and added semantic checks.
2009-07-28 16:34:15 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int SwitchStatementAST::firstToken() const
Improved ObjC parsing, and added semantic checks.
2009-07-28 16:34:15 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (switch_token)
return switch_token;
if (lparen_token)
return lparen_token;
if (condition)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = condition->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Improved ObjC parsing, and added semantic checks.
2009-07-28 16:34:15 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int SwitchStatementAST::lastToken() const
Improved ObjC parsing, and added semantic checks.
2009-07-28 16:34:15 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Improved ObjC parsing, and added semantic checks.
2009-07-28 16:34:15 +02:00
if (rparen_token)
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (condition)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = condition->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Improved ObjC parsing, and added semantic checks.
2009-07-28 16:34:15 +02:00
if (lparen_token)
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return lparen_token + 1;
if (switch_token)
return switch_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added ObjC @interface and @implementation member declarations.
2009-07-16 14:31:13 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TemplateDeclarationAST::firstToken() const
Added ObjC @interface and @implementation member declarations.
2009-07-16 14:31:13 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (export_token)
return export_token;
if (template_token)
return template_token;
if (less_token)
return less_token;
if (template_parameter_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = template_parameter_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (greater_token)
return greater_token;
if (declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Added ObjC @interface and @implementation member declarations.
2009-07-16 14:31:13 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TemplateDeclarationAST::lastToken() const
Added ObjC @interface and @implementation member declarations.
2009-07-16 14:31:13 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (declaration)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (greater_token)
return greater_token + 1;
if (template_parameter_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = template_parameter_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (less_token)
return less_token + 1;
if (template_token)
return template_token + 1;
if (export_token)
return export_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added ObjC @interface and @implementation member declarations.
2009-07-16 14:31:13 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TemplateIdAST::firstToken() const
Added ObjC @interface and @implementation member declarations.
2009-07-16 14:31:13 +02:00
{
Remember the T_TEMPLATE token we use to force the parser to recognize a template-id.
2010-08-12 12:18:49 +02:00
if (template_token)
return template_token;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (identifier_token)
return identifier_token;
if (less_token)
return less_token;
if (template_argument_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = template_argument_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (greater_token)
return greater_token;
return 0;
Added ObjC @interface and @implementation member declarations.
2009-07-16 14:31:13 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TemplateIdAST::lastToken() const
Added ObjC properties to the AST.
2009-07-16 15:50:42 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (greater_token)
return greater_token + 1;
if (template_argument_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = template_argument_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (less_token)
return less_token + 1;
if (identifier_token)
return identifier_token + 1;
Remember the T_TEMPLATE token we use to force the parser to recognize a template-id.
2010-08-12 12:18:49 +02:00
if (template_token)
return template_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added ObjC properties to the AST.
2009-07-16 15:50:42 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TemplateTypeParameterAST::firstToken() const
Added ObjC properties to the AST.
2009-07-16 15:50:42 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (template_token)
return template_token;
if (less_token)
return less_token;
if (template_parameter_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = template_parameter_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (greater_token)
return greater_token;
if (class_token)
return class_token;
if (dot_dot_dot_token)
return dot_dot_dot_token;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (equal_token)
return equal_token;
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Added ObjC properties to the AST.
2009-07-16 15:50:42 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TemplateTypeParameterAST::lastToken() const
Added ObjC properties to the AST.
2009-07-16 15:50:42 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (equal_token)
return equal_token + 1;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (dot_dot_dot_token)
return dot_dot_dot_token + 1;
if (class_token)
return class_token + 1;
if (greater_token)
return greater_token + 1;
if (template_parameter_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = template_parameter_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (less_token)
return less_token + 1;
if (template_token)
return template_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added ObjC properties to the AST.
2009-07-16 15:50:42 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ThisExpressionAST::firstToken() const
Added ObjC properties to the AST.
2009-07-16 15:50:42 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (this_token)
return this_token;
return 0;
Added ObjC properties to the AST.
2009-07-16 15:50:42 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ThisExpressionAST::lastToken() const
Added ObjC method prototypes to the AST.
2009-07-16 17:38:24 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (this_token)
return this_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added ObjC method prototypes to the AST.
2009-07-16 17:38:24 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ThrowExpressionAST::firstToken() const
Added ObjC method prototypes to the AST.
2009-07-16 17:38:24 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (throw_token)
return throw_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
}
Improved ObjC parsing, and added semantic checks.
2009-07-28 16:34:15 +02:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int ThrowExpressionAST::lastToken() const
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
{
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (throw_token)
return throw_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added ObjC method prototypes to the AST.
2009-07-16 17:38:24 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TrailingReturnTypeAST::firstToken() const
Added ObjC method prototypes to the AST.
2009-07-16 17:38:24 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (arrow_token)
return arrow_token;
if (attributes)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attributes->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Some cleanup in the C++ AST.
2010-08-26 15:55:31 +02:00
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Added ObjC method prototypes to the AST.
2009-07-16 17:38:24 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TrailingReturnTypeAST::lastToken() const
Added ObjC method prototypes to the AST.
2009-07-16 17:38:24 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Some cleanup in the C++ AST.
2010-08-26 15:55:31 +02:00
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (attributes)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attributes->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (arrow_token)
return arrow_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added ObjC method prototypes to the AST.
2009-07-16 17:38:24 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TranslationUnitAST::firstToken() const
Fixes for the ObjC AST. Now it should be complete.
2009-07-20 11:46:59 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (declaration_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Fixes for the ObjC AST. Now it should be complete.
2009-07-20 11:46:59 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TranslationUnitAST::lastToken() const
Fixes for the ObjC AST. Now it should be complete.
2009-07-20 11:46:59 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (declaration_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declaration_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Fixes for the ObjC AST. Now it should be complete.
2009-07-20 11:46:59 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TryBlockStatementAST::firstToken() const
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (try_token)
return try_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (catch_clause_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = catch_clause_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TryBlockStatementAST::lastToken() const
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (catch_clause_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = catch_clause_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (try_token)
return try_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypeConstructorCallAST::firstToken() const
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++11: Allow for typename Foo<T>{}, Foo{} and int{}. As a postfix expression. Change-Id: I65cae0571080a9fb699af61c661328ef06f97890 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-19 10:26:07 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypeConstructorCallAST::lastToken() const
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
{
C++11: Allow for typename Foo<T>{}, Foo{} and int{}. As a postfix expression. Change-Id: I65cae0571080a9fb699af61c661328ef06f97890 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-19 10:26:07 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypeIdAST::firstToken() const
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypeIdAST::lastToken() const
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypeidExpressionAST::firstToken() const
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (typeid_token)
return typeid_token;
if (lparen_token)
return lparen_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypeidExpressionAST::lastToken() const
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
return rparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
return lparen_token + 1;
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (typeid_token)
return typeid_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added more AST for ObjC.
2009-07-20 10:04:44 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypenameCallExpressionAST::firstToken() const
Added @synchronized parsing for Objective-C.
2009-07-31 16:53:05 +02:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (typename_token)
return typename_token;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
C++11: Allow for typename Foo<T>{}, Foo{} and int{}. As a postfix expression. Change-Id: I65cae0571080a9fb699af61c661328ef06f97890 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-19 10:26:07 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Added @synchronized parsing for Objective-C.
2009-07-31 16:53:05 +02:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypenameCallExpressionAST::lastToken() const
Added @synchronized parsing for Objective-C.
2009-07-31 16:53:05 +02:00
{
C++11: Allow for typename Foo<T>{}, Foo{} and int{}. As a postfix expression. Change-Id: I65cae0571080a9fb699af61c661328ef06f97890 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-19 10:26:07 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (typename_token)
return typename_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Added @synchronized parsing for Objective-C.
2009-07-31 16:53:05 +02:00
}
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypenameTypeParameterAST::firstToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (classkey_token)
return classkey_token;
if (dot_dot_dot_token)
return dot_dot_dot_token;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (equal_token)
return equal_token;
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
return 0;
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypenameTypeParameterAST::lastToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (type_id)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_id->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (equal_token)
return equal_token + 1;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (dot_dot_dot_token)
return dot_dot_dot_token + 1;
if (classkey_token)
return classkey_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypeofSpecifierAST::firstToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (typeof_token)
return typeof_token;
if (lparen_token)
return lparen_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int TypeofSpecifierAST::lastToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (rparen_token)
return rparen_token + 1;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (typeof_token)
return typeof_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int UnaryExpressionAST::firstToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (unary_op_token)
return unary_op_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
return 0;
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int UnaryExpressionAST::lastToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (unary_op_token)
return unary_op_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int UsingAST::firstToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (using_token)
return using_token;
if (typename_token)
return typename_token;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
return 0;
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int UsingAST::lastToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (semicolon_token)
return semicolon_token + 1;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (typename_token)
return typename_token + 1;
if (using_token)
return using_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int UsingDirectiveAST::firstToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (using_token)
return using_token;
if (namespace_token)
return namespace_token;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
return 0;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int UsingDirectiveAST::lastToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (semicolon_token)
return semicolon_token + 1;
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (namespace_token)
return namespace_token + 1;
if (using_token)
return using_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int WhileStatementAST::firstToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (while_token)
return while_token;
if (lparen_token)
return lparen_token;
if (condition)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = condition->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
return 0;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
}
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int WhileStatementAST::lastToken() const
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (rparen_token)
return rparen_token + 1;
if (condition)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = condition->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (while_token)
return while_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Recognize C++0x lambda expressions.
2010-03-24 12:54:25 +01:00
}
Parse C++ 0x argument packs.
2010-03-25 12:15:38 +01:00
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int GnuAttributeSpecifierAST::lastToken() const
Parse C++ 0x argument packs.
2010-03-25 12:15:38 +01:00
{
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
if (second_rparen_token)
return second_rparen_token + 1;
if (first_rparen_token)
return first_rparen_token + 1;
if (attribute_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = attribute_list->lastToken())
Regenerated firstToken/lastToken methods.
2010-06-23 16:50:11 +02:00
return candidate;
if (second_lparen_token)
return second_lparen_token + 1;
if (first_lparen_token)
return first_lparen_token + 1;
if (attribute_token)
return attribute_token + 1;
C++: fixed completion in braceless statements following a control statement. - Changed generator to generate: - Changed AST::lastToken to return 1 if there is none - Changed Bind.cpp to set the scope of the block following a control statement to extend upto (and not including) the first token after the block. So basically, including any whitespace after the control statement. Reviewed-by: Roberto Raggi
2010-09-09 15:18:17 +02:00
return 1;
Introduced IdExpressionAST.
2010-08-02 12:04:59 +02:00
}
C++: fix built-in code model to work with shared_ptr on MSVC 2017 These changes target Find Usages feature to work with shared_ptr. Improve libs/3rdparty/cplusplus and plugins/cplusplus: parse __declspec() attribute, call to variadic function template without specified template arguments, if constexpr, c++11 attributes [[value]], function templates with default parameters, resolve order for function vs template with default parameter, template operator->() with default arguments, template specialization with numeric values, find best partial specialization, fix partial specialization for non-first specialized argument Fixes: QTCREATORBUG-7866 Fixes: QTCREATORBUG-20781 Fixes: QTCREATORBUG-22857 Fixes: QTCREATORBUG-17825 Change-Id: I31a080f7729edfb2ee9650f1aff48daeba5a673b Reviewed-by: Christian Kandeler <christian.kandeler@qt.io> Reviewed-by: Nikolai Kosjar <pinaceae.pinus@gmail.com>
2020-05-14 23:07:05 +03:00
int MsvcDeclspecSpecifierAST::lastToken() const
{
if (rparen_token)
return rparen_token + 1;
if (attribute_list)
if (int candidate = attribute_list->lastToken())
return candidate;
if (lparen_token)
return lparen_token + 1;
if (attribute_token)
return attribute_token + 1;
return 1;
}
int StdAttributeSpecifierAST::lastToken() const
{
if (second_rbracket_token)
return second_rbracket_token + 1;
if (first_rbracket_token)
return first_rbracket_token + 1;
if (attribute_list)
if (int candidate = attribute_list->lastToken())
return candidate;
if (second_lbracket_token)
return second_lbracket_token + 1;
if (first_lbracket_token)
return first_lbracket_token + 1;
return 1;
}
C++: Recognize C++11 nullptr Change-Id: I5b7ac8f9b2137ffe9439ada4ec4aeb9cee8e249d Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2011-11-18 13:33:26 +01:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int PointerLiteralAST::firstToken() const
C++: Recognize C++11 nullptr Change-Id: I5b7ac8f9b2137ffe9439ada4ec4aeb9cee8e249d Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2011-11-18 13:33:26 +01:00
{
if (literal_token)
return literal_token;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int PointerLiteralAST::lastToken() const
C++: Recognize C++11 nullptr Change-Id: I5b7ac8f9b2137ffe9439ada4ec4aeb9cee8e249d Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2011-11-18 13:33:26 +01:00
{
if (literal_token)
return literal_token + 1;
return 1;
}
C++11: handle noexcept specifications. Change-Id: I7da3affea2758b2e01124105e2521e1f2c5f6678 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 11:40:01 +01:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NoExceptSpecificationAST::firstToken() const
C++11: handle noexcept specifications. Change-Id: I7da3affea2758b2e01124105e2521e1f2c5f6678 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 11:40:01 +01:00
{
if (noexcept_token)
return noexcept_token;
if (lparen_token)
return lparen_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
C++11: handle noexcept specifications. Change-Id: I7da3affea2758b2e01124105e2521e1f2c5f6678 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 11:40:01 +01:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NoExceptSpecificationAST::lastToken() const
C++11: handle noexcept specifications. Change-Id: I7da3affea2758b2e01124105e2521e1f2c5f6678 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 11:40:01 +01:00
{
if (rparen_token)
return rparen_token + 1;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
C++11: handle noexcept specifications. Change-Id: I7da3affea2758b2e01124105e2521e1f2c5f6678 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 11:40:01 +01:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (noexcept_token)
return noexcept_token + 1;
return 1;
}
C++11: add support for static_assert. Change-Id: I82d8d60acaa9265fd25e0a3734855b19bdef9c06 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 13:39:24 +01:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int StaticAssertDeclarationAST::firstToken() const
C++11: add support for static_assert. Change-Id: I82d8d60acaa9265fd25e0a3734855b19bdef9c06 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 13:39:24 +01:00
{
if (static_assert_token)
return static_assert_token;
if (lparen_token)
return lparen_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
C++11: add support for static_assert. Change-Id: I82d8d60acaa9265fd25e0a3734855b19bdef9c06 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 13:39:24 +01:00
return candidate;
if (comma_token)
return comma_token;
if (string_literal)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = string_literal->firstToken())
C++11: add support for static_assert. Change-Id: I82d8d60acaa9265fd25e0a3734855b19bdef9c06 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 13:39:24 +01:00
return candidate;
if (rparen_token)
return rparen_token;
if (semicolon_token)
return semicolon_token;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int StaticAssertDeclarationAST::lastToken() const
C++11: add support for static_assert. Change-Id: I82d8d60acaa9265fd25e0a3734855b19bdef9c06 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 13:39:24 +01:00
{
if (semicolon_token)
return semicolon_token + 1;
if (rparen_token)
return rparen_token + 1;
if (string_literal)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = string_literal->lastToken())
C++11: add support for static_assert. Change-Id: I82d8d60acaa9265fd25e0a3734855b19bdef9c06 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 13:39:24 +01:00
return candidate;
if (comma_token)
return comma_token + 1;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
C++11: add support for static_assert. Change-Id: I82d8d60acaa9265fd25e0a3734855b19bdef9c06 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-02 13:39:24 +01:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (static_assert_token)
return static_assert_token + 1;
return 1;
}
C++11: first set of changes for decltype. Change-Id: I49d6ff7eb1805cd07bdfcb27bb37d4c6cadc9115 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-10 14:41:58 +01:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DecltypeSpecifierAST::firstToken() const
C++11: first set of changes for decltype. Change-Id: I49d6ff7eb1805cd07bdfcb27bb37d4c6cadc9115 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-10 14:41:58 +01:00
{
if (decltype_token)
return decltype_token;
if (lparen_token)
return lparen_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
C++11: first set of changes for decltype. Change-Id: I49d6ff7eb1805cd07bdfcb27bb37d4c6cadc9115 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-10 14:41:58 +01:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DecltypeSpecifierAST::lastToken() const
C++11: first set of changes for decltype. Change-Id: I49d6ff7eb1805cd07bdfcb27bb37d4c6cadc9115 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-10 14:41:58 +01:00
{
if (rparen_token)
return rparen_token + 1;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
C++11: first set of changes for decltype. Change-Id: I49d6ff7eb1805cd07bdfcb27bb37d4c6cadc9115 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-10 14:41:58 +01:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (decltype_token)
return decltype_token + 1;
return 1;
}
C++: Add support for C++11 range-based 'for' loops Change-Id: I7eef048a7952a79f031ae3d0abba68e3c5ffbfb8 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-19 16:33:25 +04:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int RangeBasedForStatementAST::firstToken() const
C++: Add support for C++11 range-based 'for' loops Change-Id: I7eef048a7952a79f031ae3d0abba68e3c5ffbfb8 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-19 16:33:25 +04:00
{
if (for_token)
return for_token;
if (lparen_token)
return lparen_token;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->firstToken())
C++: Add support for C++11 range-based 'for' loops Change-Id: I7eef048a7952a79f031ae3d0abba68e3c5ffbfb8 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-19 16:33:25 +04:00
return candidate;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->firstToken())
C++: Add support for C++11 range-based 'for' loops Change-Id: I7eef048a7952a79f031ae3d0abba68e3c5ffbfb8 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-19 16:33:25 +04:00
return candidate;
if (colon_token)
return colon_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
C++: Add support for C++11 range-based 'for' loops Change-Id: I7eef048a7952a79f031ae3d0abba68e3c5ffbfb8 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-19 16:33:25 +04:00
return candidate;
if (rparen_token)
return rparen_token;
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->firstToken())
C++: Add support for C++11 range-based 'for' loops Change-Id: I7eef048a7952a79f031ae3d0abba68e3c5ffbfb8 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-19 16:33:25 +04:00
return candidate;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int RangeBasedForStatementAST::lastToken() const
C++: Add support for C++11 range-based 'for' loops Change-Id: I7eef048a7952a79f031ae3d0abba68e3c5ffbfb8 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-19 16:33:25 +04:00
{
if (statement)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = statement->lastToken())
C++: Add support for C++11 range-based 'for' loops Change-Id: I7eef048a7952a79f031ae3d0abba68e3c5ffbfb8 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-19 16:33:25 +04:00
return candidate;
if (rparen_token)
return rparen_token + 1;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
C++: Add support for C++11 range-based 'for' loops Change-Id: I7eef048a7952a79f031ae3d0abba68e3c5ffbfb8 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-19 16:33:25 +04:00
return candidate;
if (colon_token)
return colon_token + 1;
if (declarator)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = declarator->lastToken())
C++: Add support for C++11 range-based 'for' loops Change-Id: I7eef048a7952a79f031ae3d0abba68e3c5ffbfb8 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-19 16:33:25 +04:00
return candidate;
if (type_specifier_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = type_specifier_list->lastToken())
C++: Add support for C++11 range-based 'for' loops Change-Id: I7eef048a7952a79f031ae3d0abba68e3c5ffbfb8 Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>
2012-02-19 16:33:25 +04:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (for_token)
return for_token + 1;
return 1;
}
C++11: Add alignof() expression. Change-Id: Id3fb30b9a16ea724bab0d5b05e8cbddb0064e6eb Reviewed-by: hjk <qthjk@ovi.com>
2012-09-17 13:47:18 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int AlignofExpressionAST::firstToken() const
C++11: Add alignof() expression. Change-Id: Id3fb30b9a16ea724bab0d5b05e8cbddb0064e6eb Reviewed-by: hjk <qthjk@ovi.com>
2012-09-17 13:47:18 +02:00
{
if (alignof_token)
return alignof_token;
if (lparen_token)
return lparen_token;
if (typeId)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = typeId->firstToken())
C++11: Add alignof() expression. Change-Id: Id3fb30b9a16ea724bab0d5b05e8cbddb0064e6eb Reviewed-by: hjk <qthjk@ovi.com>
2012-09-17 13:47:18 +02:00
return candidate;
if (rparen_token)
return rparen_token;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int AlignofExpressionAST::lastToken() const
C++11: Add alignof() expression. Change-Id: Id3fb30b9a16ea724bab0d5b05e8cbddb0064e6eb Reviewed-by: hjk <qthjk@ovi.com>
2012-09-17 13:47:18 +02:00
{
if (rparen_token)
return rparen_token + 1;
if (typeId)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = typeId->lastToken())
C++11: Add alignof() expression. Change-Id: Id3fb30b9a16ea724bab0d5b05e8cbddb0064e6eb Reviewed-by: hjk <qthjk@ovi.com>
2012-09-17 13:47:18 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (alignof_token)
return alignof_token + 1;
return 1;
}
C++11: Parse alias declarations. The parser no longer fails declarations like: using Foo = std::vector<int>::iterator; Change-Id: Ib3a552ebbe0147fa138db6448a52cdba8f9b9207 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 10:45:10 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int AliasDeclarationAST::firstToken() const
C++11: Parse alias declarations. The parser no longer fails declarations like: using Foo = std::vector<int>::iterator; Change-Id: Ib3a552ebbe0147fa138db6448a52cdba8f9b9207 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 10:45:10 +02:00
{
if (using_token)
return using_token;
C++: add semantic support for C++11 alias decls. Task-number: QTCREATORBUG-9386 Change-Id: Ia68f3866c122ca5261dd73b2c740b47fb15744fc Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2013-05-30 12:40:08 +02:00
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->firstToken())
C++: add semantic support for C++11 alias decls. Task-number: QTCREATORBUG-9386 Change-Id: Ia68f3866c122ca5261dd73b2c740b47fb15744fc Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2013-05-30 12:40:08 +02:00
return candidate;
C++11: Parse alias declarations. The parser no longer fails declarations like: using Foo = std::vector<int>::iterator; Change-Id: Ib3a552ebbe0147fa138db6448a52cdba8f9b9207 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 10:45:10 +02:00
if (equal_token)
return equal_token;
if (typeId)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = typeId->firstToken())
C++11: Parse alias declarations. The parser no longer fails declarations like: using Foo = std::vector<int>::iterator; Change-Id: Ib3a552ebbe0147fa138db6448a52cdba8f9b9207 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 10:45:10 +02:00
return candidate;
if (semicolon_token)
return semicolon_token;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int AliasDeclarationAST::lastToken() const
C++11: Parse alias declarations. The parser no longer fails declarations like: using Foo = std::vector<int>::iterator; Change-Id: Ib3a552ebbe0147fa138db6448a52cdba8f9b9207 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 10:45:10 +02:00
{
if (semicolon_token)
return semicolon_token + 1;
if (typeId)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = typeId->lastToken())
C++11: Parse alias declarations. The parser no longer fails declarations like: using Foo = std::vector<int>::iterator; Change-Id: Ib3a552ebbe0147fa138db6448a52cdba8f9b9207 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 10:45:10 +02:00
return candidate;
if (equal_token)
return equal_token + 1;
C++: add semantic support for C++11 alias decls. Task-number: QTCREATORBUG-9386 Change-Id: Ia68f3866c122ca5261dd73b2c740b47fb15744fc Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2013-05-30 12:40:08 +02:00
if (name)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = name->lastToken())
C++: add semantic support for C++11 alias decls. Task-number: QTCREATORBUG-9386 Change-Id: Ia68f3866c122ca5261dd73b2c740b47fb15744fc Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2013-05-30 12:40:08 +02:00
return candidate;
C++11: Parse alias declarations. The parser no longer fails declarations like: using Foo = std::vector<int>::iterator; Change-Id: Ib3a552ebbe0147fa138db6448a52cdba8f9b9207 Reviewed-by: hjk <qthjk@ovi.com>
2012-09-18 10:45:10 +02:00
if (using_token)
return using_token + 1;
return 1;
}
C: Parser: Support parsing of c99 designated initializers In case: int a[6] = { [4] = 29, [2] = 15 }; struct point { int x, y; }; struct point p = { .y = 3, .x = 2 }; Grammar change when c99 language feature is enabled: old grammar: braced-init-list :: '{' initializer-list '}' new grammar: braced-init-list :: '{' designated-initializer-list '}' designated-initializer-list :: designated-initializer (',' designated-initializer )* designated-initializer :: designator* initializer-clause designator :: '.' identifier | '[' constant-expression ']' Task-number: QTCREATORBUG-1902 Change-Id: Ib99d6f553f8d0f50ba3eff86f3a2e86d73372426 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-05-05 22:56:15 +08:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DesignatedInitializerAST::firstToken() const
C: Parser: Support parsing of c99 designated initializers In case: int a[6] = { [4] = 29, [2] = 15 }; struct point { int x, y; }; struct point p = { .y = 3, .x = 2 }; Grammar change when c99 language feature is enabled: old grammar: braced-init-list :: '{' initializer-list '}' new grammar: braced-init-list :: '{' designated-initializer-list '}' designated-initializer-list :: designated-initializer (',' designated-initializer )* designated-initializer :: designator* initializer-clause designator :: '.' identifier | '[' constant-expression ']' Task-number: QTCREATORBUG-1902 Change-Id: Ib99d6f553f8d0f50ba3eff86f3a2e86d73372426 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-05-05 22:56:15 +08:00
{
if (designator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = designator_list->firstToken())
C: Parser: Support parsing of c99 designated initializers In case: int a[6] = { [4] = 29, [2] = 15 }; struct point { int x, y; }; struct point p = { .y = 3, .x = 2 }; Grammar change when c99 language feature is enabled: old grammar: braced-init-list :: '{' initializer-list '}' new grammar: braced-init-list :: '{' designated-initializer-list '}' designated-initializer-list :: designated-initializer (',' designated-initializer )* designated-initializer :: designator* initializer-clause designator :: '.' identifier | '[' constant-expression ']' Task-number: QTCREATORBUG-1902 Change-Id: Ib99d6f553f8d0f50ba3eff86f3a2e86d73372426 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-05-05 22:56:15 +08:00
return candidate;
if (equal_token)
return equal_token;
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->firstToken())
C: Parser: Support parsing of c99 designated initializers In case: int a[6] = { [4] = 29, [2] = 15 }; struct point { int x, y; }; struct point p = { .y = 3, .x = 2 }; Grammar change when c99 language feature is enabled: old grammar: braced-init-list :: '{' initializer-list '}' new grammar: braced-init-list :: '{' designated-initializer-list '}' designated-initializer-list :: designated-initializer (',' designated-initializer )* designated-initializer :: designator* initializer-clause designator :: '.' identifier | '[' constant-expression ']' Task-number: QTCREATORBUG-1902 Change-Id: Ib99d6f553f8d0f50ba3eff86f3a2e86d73372426 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-05-05 22:56:15 +08:00
return candidate;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DesignatedInitializerAST::lastToken() const
C: Parser: Support parsing of c99 designated initializers In case: int a[6] = { [4] = 29, [2] = 15 }; struct point { int x, y; }; struct point p = { .y = 3, .x = 2 }; Grammar change when c99 language feature is enabled: old grammar: braced-init-list :: '{' initializer-list '}' new grammar: braced-init-list :: '{' designated-initializer-list '}' designated-initializer-list :: designated-initializer (',' designated-initializer )* designated-initializer :: designator* initializer-clause designator :: '.' identifier | '[' constant-expression ']' Task-number: QTCREATORBUG-1902 Change-Id: Ib99d6f553f8d0f50ba3eff86f3a2e86d73372426 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-05-05 22:56:15 +08:00
{
if (initializer)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = initializer->lastToken())
C: Parser: Support parsing of c99 designated initializers In case: int a[6] = { [4] = 29, [2] = 15 }; struct point { int x, y; }; struct point p = { .y = 3, .x = 2 }; Grammar change when c99 language feature is enabled: old grammar: braced-init-list :: '{' initializer-list '}' new grammar: braced-init-list :: '{' designated-initializer-list '}' designated-initializer-list :: designated-initializer (',' designated-initializer )* designated-initializer :: designator* initializer-clause designator :: '.' identifier | '[' constant-expression ']' Task-number: QTCREATORBUG-1902 Change-Id: Ib99d6f553f8d0f50ba3eff86f3a2e86d73372426 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-05-05 22:56:15 +08:00
return candidate;
if (equal_token)
return equal_token + 1;
if (designator_list)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = designator_list->lastToken())
C: Parser: Support parsing of c99 designated initializers In case: int a[6] = { [4] = 29, [2] = 15 }; struct point { int x, y; }; struct point p = { .y = 3, .x = 2 }; Grammar change when c99 language feature is enabled: old grammar: braced-init-list :: '{' initializer-list '}' new grammar: braced-init-list :: '{' designated-initializer-list '}' designated-initializer-list :: designated-initializer (',' designated-initializer )* designated-initializer :: designator* initializer-clause designator :: '.' identifier | '[' constant-expression ']' Task-number: QTCREATORBUG-1902 Change-Id: Ib99d6f553f8d0f50ba3eff86f3a2e86d73372426 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-05-05 22:56:15 +08:00
return candidate;
return 1;
}
C++: Split designator AST Change-Id: I9bfed2023624c818c0f35f24476693cffeaf2bbc Reviewed-by: Wang Hoi <wanghoi@126.com> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-06-20 09:57:46 +03:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BracketDesignatorAST::firstToken() const
C++: Split designator AST Change-Id: I9bfed2023624c818c0f35f24476693cffeaf2bbc Reviewed-by: Wang Hoi <wanghoi@126.com> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-06-20 09:57:46 +03:00
{
if (lbracket_token)
return lbracket_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
C++: Split designator AST Change-Id: I9bfed2023624c818c0f35f24476693cffeaf2bbc Reviewed-by: Wang Hoi <wanghoi@126.com> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-06-20 09:57:46 +03:00
return candidate;
if (rbracket_token)
return rbracket_token;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int BracketDesignatorAST::lastToken() const
C++: Split designator AST Change-Id: I9bfed2023624c818c0f35f24476693cffeaf2bbc Reviewed-by: Wang Hoi <wanghoi@126.com> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-06-20 09:57:46 +03:00
{
if (rbracket_token)
return rbracket_token + 1;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
C++: Split designator AST Change-Id: I9bfed2023624c818c0f35f24476693cffeaf2bbc Reviewed-by: Wang Hoi <wanghoi@126.com> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-06-20 09:57:46 +03:00
return candidate;
if (lbracket_token)
return lbracket_token + 1;
return 1;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DotDesignatorAST::firstToken() const
C++: Split designator AST Change-Id: I9bfed2023624c818c0f35f24476693cffeaf2bbc Reviewed-by: Wang Hoi <wanghoi@126.com> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-06-20 09:57:46 +03:00
{
if (dot_token)
return dot_token;
if (identifier_token)
return identifier_token;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int DotDesignatorAST::lastToken() const
C++: Split designator AST Change-Id: I9bfed2023624c818c0f35f24476693cffeaf2bbc Reviewed-by: Wang Hoi <wanghoi@126.com> Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-06-20 09:57:46 +03:00
{
if (identifier_token)
return identifier_token + 1;
if (dot_token)
return dot_token + 1;
C: Parser: Support parsing of c99 designated initializers In case: int a[6] = { [4] = 29, [2] = 15 }; struct point { int x, y; }; struct point p = { .y = 3, .x = 2 }; Grammar change when c99 language feature is enabled: old grammar: braced-init-list :: '{' initializer-list '}' new grammar: braced-init-list :: '{' designated-initializer-list '}' designated-initializer-list :: designated-initializer (',' designated-initializer )* designated-initializer :: designator* initializer-clause designator :: '.' identifier | '[' constant-expression ']' Task-number: QTCREATORBUG-1902 Change-Id: Ib99d6f553f8d0f50ba3eff86f3a2e86d73372426 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-05-05 22:56:15 +08:00
return 1;
}
C++: Support alignas in C++11 mode. Change-Id: Ifa81a481bf92b5b71495a105ae292f3e9895f704 Task-number: QTCREATORBUG-9279 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-07-15 12:37:19 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int AlignmentSpecifierAST::firstToken() const
C++: Support alignas in C++11 mode. Change-Id: Ifa81a481bf92b5b71495a105ae292f3e9895f704 Task-number: QTCREATORBUG-9279 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-07-15 12:37:19 +02:00
{
if (align_token)
return align_token;
if (lparen_token)
return lparen_token;
if (typeIdExprOrAlignmentExpr)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = typeIdExprOrAlignmentExpr->firstToken())
C++: Support alignas in C++11 mode. Change-Id: Ifa81a481bf92b5b71495a105ae292f3e9895f704 Task-number: QTCREATORBUG-9279 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-07-15 12:37:19 +02:00
return candidate;
if (ellipses_token)
return ellipses_token;
if (rparen_token)
return rparen_token;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int AlignmentSpecifierAST::lastToken() const
C++: Support alignas in C++11 mode. Change-Id: Ifa81a481bf92b5b71495a105ae292f3e9895f704 Task-number: QTCREATORBUG-9279 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-07-15 12:37:19 +02:00
{
if (rparen_token)
return rparen_token + 1;
if (ellipses_token)
return ellipses_token + 1;
if (typeIdExprOrAlignmentExpr)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = typeIdExprOrAlignmentExpr->lastToken())
C++: Support alignas in C++11 mode. Change-Id: Ifa81a481bf92b5b71495a105ae292f3e9895f704 Task-number: QTCREATORBUG-9279 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>
2014-07-15 12:37:19 +02:00
return candidate;
if (lparen_token)
return lparen_token + 1;
if (align_token)
return align_token + 1;
return 1;
}
C++: Support noexcept operator The code model failed to parse the noexcept operator which is often used in noexcept specifiers, e.g.: "void f() noexcept(noexcept(g()));" Consequently some c++11 headers such as unordered_map, array and unordered_set could not be parsed and no code completition was available. I have created the NoExceptOperatorExpressionAST class which is created whenever a noexcept token is found in an expression with operator precedence. The noExcept test case in the cplusplus/cxx11 test now contains a function that uses the noexcept operator. Fixed noexcept operator parsing Added the test requested by Sergey Shambir, which then revealed that i had not implemeneted the noexpect operator parsing according to the c++ specification. As stated here http://cpp0x.centaur.ath.cx/expr.unary.noexcept.html the noexcept operator is a unary-expression that contains an expression (and not a constant-expression). This should now be fixed. Change-Id: Id4a99a43b660bd83e7680274491d99a698b57094 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
2015-07-22 11:08:01 +02:00
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NoExceptOperatorExpressionAST::firstToken() const
C++: Support noexcept operator The code model failed to parse the noexcept operator which is often used in noexcept specifiers, e.g.: "void f() noexcept(noexcept(g()));" Consequently some c++11 headers such as unordered_map, array and unordered_set could not be parsed and no code completition was available. I have created the NoExceptOperatorExpressionAST class which is created whenever a noexcept token is found in an expression with operator precedence. The noExcept test case in the cplusplus/cxx11 test now contains a function that uses the noexcept operator. Fixed noexcept operator parsing Added the test requested by Sergey Shambir, which then revealed that i had not implemeneted the noexpect operator parsing according to the c++ specification. As stated here http://cpp0x.centaur.ath.cx/expr.unary.noexcept.html the noexcept operator is a unary-expression that contains an expression (and not a constant-expression). This should now be fixed. Change-Id: Id4a99a43b660bd83e7680274491d99a698b57094 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
2015-07-22 11:08:01 +02:00
{
if (noexcept_token)
return noexcept_token;
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->firstToken())
C++: Support noexcept operator The code model failed to parse the noexcept operator which is often used in noexcept specifiers, e.g.: "void f() noexcept(noexcept(g()));" Consequently some c++11 headers such as unordered_map, array and unordered_set could not be parsed and no code completition was available. I have created the NoExceptOperatorExpressionAST class which is created whenever a noexcept token is found in an expression with operator precedence. The noExcept test case in the cplusplus/cxx11 test now contains a function that uses the noexcept operator. Fixed noexcept operator parsing Added the test requested by Sergey Shambir, which then revealed that i had not implemeneted the noexpect operator parsing according to the c++ specification. As stated here http://cpp0x.centaur.ath.cx/expr.unary.noexcept.html the noexcept operator is a unary-expression that contains an expression (and not a constant-expression). This should now be fixed. Change-Id: Id4a99a43b660bd83e7680274491d99a698b57094 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
2015-07-22 11:08:01 +02:00
return candidate;
return 0;
}
/** \generated */
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
int NoExceptOperatorExpressionAST::lastToken() const
C++: Support noexcept operator The code model failed to parse the noexcept operator which is often used in noexcept specifiers, e.g.: "void f() noexcept(noexcept(g()));" Consequently some c++11 headers such as unordered_map, array and unordered_set could not be parsed and no code completition was available. I have created the NoExceptOperatorExpressionAST class which is created whenever a noexcept token is found in an expression with operator precedence. The noExcept test case in the cplusplus/cxx11 test now contains a function that uses the noexcept operator. Fixed noexcept operator parsing Added the test requested by Sergey Shambir, which then revealed that i had not implemeneted the noexpect operator parsing according to the c++ specification. As stated here http://cpp0x.centaur.ath.cx/expr.unary.noexcept.html the noexcept operator is a unary-expression that contains an expression (and not a constant-expression). This should now be fixed. Change-Id: Id4a99a43b660bd83e7680274491d99a698b57094 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
2015-07-22 11:08:01 +02:00
{
if (expression)
Standardize on int for line and column values Recently tons of warnings show up for presumably "problematic" singned <-> unsigned and size conversions. The Qt side uses 'int', and that's the biggest 'integration surface' for us, so instead of establishing some internal boundary between signed and unsigned areas, push that boundary out of creator core code, and use 'int' everywhere. Because it reduces friction further, also do it in libcplusplus. Change-Id: I84f3b79852c8029713e7ea6f133ffb9ef7030a70 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@qt.io>
2019-07-24 18:40:10 +02:00
if (int candidate = expression->lastToken())
C++: Support noexcept operator The code model failed to parse the noexcept operator which is often used in noexcept specifiers, e.g.: "void f() noexcept(noexcept(g()));" Consequently some c++11 headers such as unordered_map, array and unordered_set could not be parsed and no code completition was available. I have created the NoExceptOperatorExpressionAST class which is created whenever a noexcept token is found in an expression with operator precedence. The noExcept test case in the cplusplus/cxx11 test now contains a function that uses the noexcept operator. Fixed noexcept operator parsing Added the test requested by Sergey Shambir, which then revealed that i had not implemeneted the noexpect operator parsing according to the c++ specification. As stated here http://cpp0x.centaur.ath.cx/expr.unary.noexcept.html the noexcept operator is a unary-expression that contains an expression (and not a constant-expression). This should now be fixed. Change-Id: Id4a99a43b660bd83e7680274491d99a698b57094 Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>
2015-07-22 11:08:01 +02:00
return candidate;
if (noexcept_token)
return noexcept_token + 1;
return 1;
}
CPlusPlus: Handle C++20 concepts in parser Change-Id: I8c6b8b1ba3f36b83cd1d667bec9830271147b1ac Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: <github-actions-qt-creator@cristianadam.eu> Reviewed-by: Christian Stenger <christian.stenger@qt.io>
2023-02-09 15:11:14 +01:00
int TypeConstraintAST::firstToken() const
{
if (nestedName)
return nestedName->firstToken();
return conceptName->firstToken();
}
int TypeConstraintAST::lastToken() const
{
if (greaterToken)
return greaterToken + 1;
return conceptName->lastToken();
}
int PlaceholderTypeSpecifierAST::firstToken() const
{
if (typeConstraint)
return typeConstraint->firstToken();
if (declTypetoken)
return declTypetoken;
return autoToken;
}
int PlaceholderTypeSpecifierAST::lastToken() const
{
if (rparenToken)
return rparenToken + 1;
return autoToken + 1;
}
Copy Permalink