- 24 Feb, 2014 2 commits
-
-
Orgad Shaneh authored
Task-number: QTCREATORBUG-11216 Change-Id: Iac10e75f0f5c504b79e8466607dc1f478e578f99 Reviewed-by:
Erik Verbruggen <erik.verbruggen@digia.com>
-
Orgad Shaneh authored
Change-Id: I87d6e76be3030e617603209c3a1b8b3c476cf1f6 Reviewed-by:
Nikolai Kosjar <nikolai.kosjar@digia.com>
-
- 08 Jan, 2014 1 commit
-
-
Robert Loehning authored
Change-Id: Ib5423fdd064e4546f848c0b640b0ed0514c26d3a Reviewed-by:
Leena Miettinen <riitta-leena.miettinen@digia.com> Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 03 Dec, 2013 1 commit
-
-
Nikolai Kosjar authored
This takes too much memory. For qtcreator.pro the numbers are as follows: Patch applied: ~ 1600MB (RES) Patch reverted: ~ 510MB (RES) This reverts commit 4c2daa90. Task-number: QTCREATORBUG-10973 Change-Id: I843bd7c1ea4a26a1ec55ddc14c2a34a98d040922 Reviewed-by:
hjk <hjk121@nokiamail.com> Reviewed-by:
Robert Loehning <robert.loehning@digia.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com> Reviewed-by:
Orgad Shaneh <orgads@gmail.com> Reviewed-by:
Erik Verbruggen <erik.verbruggen@digia.com>
-
- 29 Nov, 2013 2 commits
-
-
Nikolai Kosjar authored
This adds definitions for the macros __FILE__, __LINE__, __DATE__ and __TIME__ on demand. As a side effect, this also introduces highlighting for the uses of these macros. Task-number: QTCREATORBUG-8036 Change-Id: Ib7546c7d45d2eecbc50c7883fc684e3497154405 Reviewed-by:
Erik Verbruggen <erik.verbruggen@digia.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com> Reviewed-by:
hjk <hjk121@nokiamail.com>
-
Nikolai Kosjar authored
Breaks highlighting for macros using the predefined macros. This reverts commit 1d834c11. Change-Id: Ic13c407e293a806a63ff30153864530df6a32e47 Reviewed-by:
hjk <hjk121@nokiamail.com> Reviewed-by:
Erik Verbruggen <erik.verbruggen@digia.com>
-
- 28 Nov, 2013 1 commit
-
-
Simon Schäfer authored
Preprocessor variables __LINE__,__FILE__,__TIME__,__DATE__ where destroying the following systems when affected variables were standing within the same line with those variables: * highlighting * refactoring * local renaming Task-number: QTCREATORBUG-8036 Change-Id: I1a4b919d15812872ca5a8e63b1031ec1ab144c22 Reviewed-by:
Nikolai Kosjar <nikolai.kosjar@digia.com>
-
- 10 Oct, 2013 1 commit
-
-
Nikolai Kosjar authored
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 872bfb70. Change-Id: Icb65e8d73b59a022f8885b14df497169543a3b92 Reviewed-by:
hjk <hjk121@nokiamail.com>
-
- 12 Sep, 2013 1 commit
-
-
Friedemann Kleint authored
Change-Id: Ibe6f41ac15df1ec685b0d0766ff568abf6f3ae7e Reviewed-by:
Nikolai Kosjar <nikolai.kosjar@digia.com>
-
- 17 Jul, 2013 1 commit
-
-
Orgad Shaneh authored
Change-Id: I1309db70e98d678e150388c76ce665e988fdf081 Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
- 11 Jun, 2013 1 commit
-
-
Erik Verbruggen authored
By lexing the first token after a macro call (meaning: the token after the closing parenthesis (which was passed to handleFunctionLikeMacro which in turn pushed it back into the token buffer)), a token buffer might be popped, which unblocks the macro that generated the actual param pack. The effect was that if this happens in the expansion of a recursive macro (with parameters!), the preprocessor ended up in an infinite loop. Task-number: QTCREATORBUG-9015 Task-number: QTCREATORBUG-9447 Change-Id: I0d83c59188ec15c4a948970e9fa944a17d765475 Reviewed-by:
Nikolai Kosjar <nikolai.kosjar@digia.com>
-
- 03 Jun, 2013 1 commit
-
-
Erik Verbruggen authored
Moved it from the handleIfDefDirective to the pre-defined macros, so that #if defined() can also see it. Task-number: QTCREATORBUG-9322 Change-Id: Icbecad5c885dd2374b559969c99631c3ddc73844 Reviewed-by:
Nikolai Kosjar <nikolai.kosjar@digia.com>
-
- 30 May, 2013 1 commit
-
-
Erik Verbruggen authored
Doing so resulted in an incorrect position for the EOF token when the preprocessed output would be parsed. That in turn leads to incorrect insertion positions for refactoring actions. This is especially true when a file contains only preprocessor directives: the EOF token would point to line 1 column 1, which is usually not the place where code should be inserted. Change-Id: I7d359aa7a6c04bc52c8b873fd49ad6afc3a77319 Reviewed-by:
hjk <hjk121@nokiamail.com>
-
- 29 Apr, 2013 1 commit
-
-
Francois Ferrand authored
Preprocessor did not correctly handle when variadic macro arguments were not provided at all, if there were other arguments: macro was not expanded in case only the non variadic arguments were given. #define MACRO(...) used to work fine for 0 or more arguments. #define MACRO(ARG0, ...) used to work only for 2 or more arguments, now fixed. Change-Id: I64e9199ceccae05618a49931c2adad8e4f9471ba Reviewed-by:
Nikolai Kosjar <nikolai.kosjar@digia.com>
-
- 19 Apr, 2013 1 commit
-
-
hjk authored
Change-Id: I45399a196500cbc6aecedfaa94a50890914906f1 Reviewed-by:
Erik Verbruggen <erik.verbruggen@digia.com>
-
- 16 Apr, 2013 2 commits
-
-
hjk authored
Change-Id: If86c73945808e871f60fdf231b91e02f66bd1b32 Reviewed-by:
Erik Verbruggen <erik.verbruggen@digia.com>
-
hjk authored
Change-Id: I896423172aed0e19feaaf9144ed5f18ba99c720b Reviewed-by:
Erik Verbruggen <erik.verbruggen@digia.com>
-
- 08 Apr, 2013 1 commit
-
-
Erik Verbruggen authored
This prevents a whole lot of re-allocations when the output byte array needs to grow. It also prevents some heap fragmentation for big files. Because the preprocessed output is short lived (it will be parsed immediately after, and then discarded), it is not squeezed to the minimal size. This would result in another allocation. Change-Id: I4974be5144f88cdfc4ddc9d8330200725aa90803 Reviewed-by:
hjk <hjk121@nokiamail.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
- 03 Apr, 2013 1 commit
-
-
Oswald Buddenhagen authored
... and adjust INCLUDEPATH accordingly. while i'm at messing with include statements, also re-order the include blocks according to policy and sort them within bigger blocks. Change-Id: I7762abfd7c4ecf59432b99db2f424e4fa25733a5 Reviewed-by:
Tobias Hunger <tobias.hunger@digia.com> Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
- 22 Feb, 2013 1 commit
-
-
Tobias Hunger authored
Change-Id: I37bc8f9bc874de52281b8597838ef8addae1a1a3 Reviewed-by:
Tobias Hunger <tobias.hunger@digia.com>
-
- 29 Jan, 2013 1 commit
-
-
Robert Loehning authored
Change-Id: Ic6a9ff0359625021ebc061d22db6811814534205 Reviewed-by:
Kai Koehne <kai.koehne@digia.com>
-
- 18 Jan, 2013 2 commits
-
-
Erik Verbruggen authored
Track the typical #ifndef/#define/#endif usage in header files to see if the macro is an include guard. If so, store it in the Document. No behavioural change, just recording the name. This can be used in the future to track if a file needs to be re-parsed when a macro changes: if it was used in the file, and not defined in it nor being the include-guard, a file should be re-preprocessed and re-parsed. It can also be used to check if two files have the same include guard. Change-Id: I2715f529997a7b24a11bdbc6150652e2669f1a46 Reviewed-by:
Nikolai Kosjar <nikolai.kosjar@digia.com>
-
Francois Ferrand authored
When in 'keep comments' mode, the preprocessor does not properly handle macro calls with comments between the macro name and the opening parenthesis: "FOO /*something to say*/ (45)". Change-Id: I6fe733242e4d2ccff2985d17399d0a084917415a Reviewed-by:
Erik Verbruggen <erik.verbruggen@digia.com>
-
- 11 Jan, 2013 2 commits
-
-
Erik Verbruggen authored
- Fixed blocking macro check - Enabled buffer "compression": when tokens are generated and no new macro is being blocked, then prepend the tokens to the previous buffer. This happens a lot when undo-ing look-ahead. - Added documentation Change-Id: I6fa816d94ce4696e473bdbc4f3bf477d77e4dd51 Reviewed-by:
Nikolai Kosjar <nikolai.kosjar@digia.com>
-
hjk authored
This does not yet resolve the file using the proper mechanism. Change-Id: I04913e8b01ae0c3411961f0c1cffe07202f06a0a Reviewed-by:
Erik Verbruggen <erik.verbruggen@digia.com>
-
- 08 Jan, 2013 1 commit
-
-
Orgad Shaneh authored
#!/usr/bin/env ruby Dir.glob('**/*.cpp') { |file| # skip ast (excluding paste, astpath, and canv'ast'imer) next if file =~ /ast[^eip]|keywords\.|qualifiers|preprocessor|names.cpp/i s = File.read(file) next if s.include?('qlalr') orig = s.dup s.gsub!(/\n *if [^\n]*{\n[^\n]*\n\s+}(\s+else if [^\n]* {\n[^\n]*\n\s+})*(\s+else {\n[^\n]*\n\s+})?\n/m) { |m| res = $& if res =~ /^\s*(\/\/|[A-Z_]{3,})/ # C++ comment or macro (Q_UNUSED, SDEBUG), do not touch braces res else res.gsub!('} else', 'else') res.gsub!(/\n +} *\n/m, "\n") res.gsub(/ *{$/, '') end } s.gsub!(/ *$/, '') File.open(file, 'wb').write(s) if s != orig } Change-Id: I3b30ee60df0986f66c02132c65fc38a3fbb6bbdc Reviewed-by:
hjk <qthjk@ovi.com>
-
- 20 Dec, 2012 1 commit
-
-
hjk authored
Turns out QByteArray::setNum() is unnecessarily slow (will be fixed independently), but even then, we can be faster. Change-Id: I663bd2b8cc844bbe800879bccfa57999d020ba3b Reviewed-by:
Erik Verbruggen <erik.verbruggen@digia.com>
-
- 04 Dec, 2012 1 commit
-
-
Erik Verbruggen authored
Change-Id: Ibe4cc69eafd14dab7707862b1068ce1e21b1d8e0 Reviewed-by:
Nikolai Kosjar <nikolai.kosjar@digia.com>
-
- 15 Oct, 2012 1 commit
-
-
Erik Verbruggen authored
Record revisions of documents in macro definitions and usages. Then, when searching for usages, check the revision of the documents against the revision of the macros. If they are out-of-sync, repreprocess the documents to get up-to-date info. Task-number: QTCREATORBUG-7872 Change-Id: I846bb52ec660024728ab117a9fb7e43382a50e63 Reviewed-by:
Christian Stenger <christian.stenger@digia.com>
-
- 05 Oct, 2012 1 commit
-
-
hjk authored
Change-Id: Ice592c6de9951ee3b2c4cb52ed0bb3b6770e0825 Reviewed-by:
Eike Ziller <eike.ziller@digia.com>
-
- 19 Sep, 2012 1 commit
-
-
Nikolai Kosjar authored
This addresses the main memory leak revealed in QTCREATORBUG-7645. The other leaks seem to have their origin in Qt. Task-Number: QTCREATORBUG-7645. Change-Id: I77f45449416c143b222ed5f5c905cba9674f95bb Reviewed-by:
Christian Kamm <kamm@incasoftware.de>
-
- 11 Sep, 2012 1 commit
-
-
Leandro Melo authored
Even if "expand funcion-like macros" is unset we still perform the expansion in the case it's already doing so - when it originally started from an object-like macro. Task-number: QTCREATORBUG-7712 Change-Id: Ie2a24de227f757d195146477d48246472082d28a Reviewed-by:
Orgad Shaneh <orgads@gmail.com> Reviewed-by:
hjk <qthjk@ovi.com>
-
- 05 Sep, 2012 1 commit
-
-
Leandro Melo authored
Task-number: QTCREATORBUG-7815 Change-Id: Id3e6b018bfd58b0f0072c637d69721a4bde1603a Reviewed-by:
Orgad Shaneh <orgads@gmail.com> Reviewed-by:
Eike Ziller <eike.ziller@nokia.com>
-
- 29 Aug, 2012 1 commit
-
-
Leandro Melo authored
Task-number: QTCREATORBUG-7780 Change-Id: Ie93704feff17ad8229e50fb1133048f2c7598dea Reviewed-by:
Orgad Shaneh <orgads@gmail.com> Reviewed-by:
hjk <qthjk@ovi.com>
-
- 23 Aug, 2012 2 commits
-
-
Leandro Melo authored
Notice that a similar problem still exists for which we need to fix the lexer when there's a C style commend which ends with a backslash-newline. Task-number: QTCREATORBUG-7713 Change-Id: I0f6d561703984f917fa5ed29de020ad0bdc5aaf0 Reviewed-by:
David Schulz <david.schulz@nokia.com> Reviewed-by:
hjk <qthjk@ovi.com>
-
Leandro Melo authored
It was creating extra line(s)... Change-Id: If28a9ccf16195c71747479db838a5589ea6683a0 Reviewed-by:
Roberto Raggi <roberto.raggi@nokia.com>
-
- 07 Aug, 2012 2 commits
-
-
Christian Kamm authored
Task-number: QTCREATORBUG-7702 Change-Id: I0ec2e1eb9bf1c556b0a426d4405df1c48b5653ed Reviewed-by:
Leandro Melo <leandro.melo@nokia.com>
-
Christian Kamm authored
Task-number: QTCREATORBUG-7512 Change-Id: I59898a0449f1f6997963e0f31c47293358a773f6 Reviewed-by:
Leandro Melo <leandro.melo@nokia.com>
-
- 06 Aug, 2012 1 commit
-
-
hjk authored
More uniform. Change-Id: I1c6057981f4c2b3170a4e69f0674fe4caf1143a2 Reviewed-by:
Robert Loehning <robert.loehning@nokia.com>
-
- 19 Jul, 2012 1 commit
-
-
Eike Ziller authored
Change-Id: I7134d7de30bcf9f9dcfad42520dd45ee083a852d Reviewed-by:
Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
-