Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Forgot to remove some dead code | Dimitri van Heesch | 2020-09-11 | 1 | -14/+0 |
| | |||||
* | Split into separate rules | Dimitri van Heesch | 2020-09-11 | 1 | -5164/+5183 |
| | | | | Also replaced tabs by spaces and removed trailing whitespace | ||||
* | issue #8017 C++: mishandling of brackets used in trailing return types | albert-github | 2020-09-08 | 1 | -0/+16 |
| | | | | Handle `{` and `;` inside, nested, round brackets not as end of return type | ||||
* | Merge pull request #7981 from albert-github/feature/bug_647654 | Dimitri van Heesch | 2020-08-30 | 1 | -4/+11 |
|\ | | | | | bug_647654 Special command \fn fails when first argument of PHP function is call-by-reference | ||||
| * | bug_647654 Special command \fn fails when first argument of PHP function is ↵ | albert-github | 2020-08-28 | 1 | -4/+11 |
| | | | | | | | | | | | | | | | | | | | | | | call-by-reference The handling of `(&$var` for php was not included at all places. It was handled with the rules (in scanner.l): ``` <FindMembers>"("/{BN}*"::"*{BN}*({TSCOPE}{BN}*"::")*{TSCOPE}{BN}*")"{BN}*"(" | /* typedef void (A<int>::func_t)(args...) */$ <FindMembers>("("({BN}*"::"*{BN}*{TSCOPE}{BN}*"::")*({BN}*[*&\^]{BN}*)+)+ { /* typedef void (A::*ptr_t)(args...) or int (*fun c(int))[], the ^ is for Obj-C blocks */$ ``` | ||||
* | | issue #7979: C++ enums being defined in multiple files after b265433 ↵ | Dimitri van Heesch | 2020-08-28 | 1 | -8/+8 |
|/ | | | | (multi-thread input processing) | ||||
* | Fixed issue that could cause wrong line numbers | Dimitri van Heesch | 2020-08-06 | 1 | -1/+4 |
| | |||||
* | More minor tweaks | Dimitri van Heesch | 2020-07-28 | 1 | -3/+1 |
| | |||||
* | issue #7923 source line numbers in warnings output by parser are off by 1 | albert-github | 2020-07-27 | 1 | -1/+3 |
| | | | | Explicit counting of the removed newlines at the beginning of a documenation block (markdown.cpp) so this number can be added to get a better line number in case of warnings. | ||||
* | Refactor: Modernize clang parser and make it run with multiple threads | Dimitri van Heesch | 2020-07-16 | 1 | -43/+18 |
| | |||||
* | Fixed anothing compilation issue when use_libclang was not enabled | Dimitri van Heesch | 2020-06-29 | 1 | -16/+12 |
| | |||||
* | Refactor: make preprocessor run in parallel | Dimitri van Heesch | 2020-06-28 | 1 | -14/+17 |
| | | | | | And at the same time make sure it gives the same results as when processed using a single thread. | ||||
* | Refactor: modernize markdown and make it thread-safe | Dimitri van Heesch | 2020-06-16 | 1 | -4/+8 |
| | |||||
* | Merge pull request #7742 from albert-github/feature/issue_7734 | Dimitri van Heesch | 2020-05-09 | 1 | -16/+20 |
|\ | | | | | issue #7734 Incorrect parsing of Q_PROPERTY | ||||
| * | issue #7734 Incorrect parsing of Q_PROPERTY | albert-github | 2020-05-01 | 1 | -16/+20 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The parsing of the type / name was not done correctly as the name `{ID}` is also part of the `{TSCOPE}` and hence the name was seen as a type. The name is the last part before an attribute is present. Missing other parts: - parsing of `*` - not parsing of a number of (not supported attributes) The definition of `Q_PROPERTY` is: ``` Q_PROPERTY(type name (READ getFunction [WRITE setFunction] | MEMBER memberName [(READ getFunction | WRITE setFunction)]) [RESET resetFunction] [NOTIFY notifySignal] [REVISION int] [DESIGNABLE bool] [SCRIPTABLE bool] [STORED bool] [USER bool] [CONSTANT] [FINAL]) ``` Note: in the implementation we do not enforce the order of the attributes. | ||||
* | | issue #7747 Three-way comparison operator | albert-github | 2020-05-04 | 1 | -1/+1 |
| | | | | | | | | Implementation of the C++2x three-way / spaceship operator. | ||||
* | | Input buffer overflow in php input code (#7745) | albert-github | 2020-05-02 | 1 | -4/+4 |
|/ | | | | | | | | When having a very long initialization line in php code we get the message: ``` input buffer overflow, can't enlarge buffer because scanner uses REJECT ``` In this case the, easy, solution is to split, in the lexer, the input based on the commas. | ||||
* | Refactoring: replace Doxygen::namespaceAliasDict by Doxygen::namespaceAliasMap | Dimitri van Heesch | 2020-04-29 | 1 | -12/+4 |
| | |||||
* | Refactor: improve encapsulation for ArgumentList | Dimitri van Heesch | 2020-04-25 | 1 | -19/+15 |
| | |||||
* | Performance improvements after profiling | Dimitri van Heesch | 2020-04-24 | 1 | -4/+4 |
| | | | | | In some cases performance dropped when upgrading from version 1.8.16 to 1.8.17 or 1.8.18. With these changes the performance should be back to normal again. | ||||
* | issue #7635: Incorrect location for enum in XML file | Dimitri van Heesch | 2020-03-14 | 1 | -6/+54 |
| | |||||
* | Enabled stricter compiler warnings and fixed all new warnings | Dimitri van Heesch | 2020-03-08 | 1 | -5/+10 |
| | |||||
* | Incorrect handling of typedef in combination with const | albert-github | 2020-02-25 | 1 | -3/+10 |
| | | | | | | | | | | | | | | | | | | | | | I issue #7060 and example was given with ``` typedef const char m_msgEvtName; ``` we see that - 1.8.15, listed under Typedefs: ` typedef const char m_msgEvtName` - 1.8.16 and up, listed under Variables: `const typedef char m_msgEvtName` so mentioned: - wrong "header" - const at the wrong place This is a regression on: C# consts incorrectly placed under instance variables (Origin: bugzilla #535853) (issue #2976) and the pull request #7048 The fix should only be used for C# | ||||
* | issue #6319: C++ function returning std::function with reference argument is ↵ | Dimitri van Heesch | 2020-02-17 | 1 | -15/+16 |
| | | | | not recognized as a function (Origin: bugzilla #792830) | ||||
* | Fix compiler warnings on Windows (Visual Studio) | Dimitri van Heesch | 2020-02-12 | 1 | -0/+3 |
| | |||||
* | issue #7508: TYPEDEF_HIDES_STRUCT stopped working properly | Dimitri van Heesch | 2020-01-28 | 1 | -5/+3 |
| | |||||
* | Move DocGroup inside CommentScanner instead of using a global | Dimitri van Heesch | 2020-01-26 | 1 | -8/+8 |
| | |||||
* | Cleanup unused/unwanted parser dependencies on code generator | Dimitri van Heesch | 2020-01-26 | 1 | -1/+0 |
| | |||||
* | Merge pull request #7497 from albert-github/feature/bug_consistency_only | Dimitri van Heesch | 2020-01-11 | 1 | -4/+4 |
|\ | | | | | Consistency `\*only` and `\end*only` commands | ||||
| * | Consistency `\*only` and `\end*only` commands | albert-github | 2020-01-09 | 1 | -4/+4 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Not all possibilities in respect of `\*only` and `\end*only` commands were present which could lead to messages like: ``` .../aa.h:4: warning: reached end of comment while inside a \rtfonly block; check for missing \endrtfonly tag! ../.aa.h:4: warning: rtfonly section ended without end marker .../aa.h:4: warning: rtfonly section ended without end marker ``` in case of a problem like: ``` /** \file * \rtfonly * RTF /* Nested */ * \endrtfonly */ ``` | ||||
* | | issue #7472: Serious regression: /**< comments cause functions to be ↵ | Dimitri van Heesch | 2020-01-09 | 1 | -5/+3 |
|/ | | | | silently ignored | ||||
* | Make commentscan.l reentrant | Dimitri van Heesch | 2019-12-30 | 1 | -3/+5 |
| | |||||
* | Merge branch 'master' into feature/bug_fenced_code | Dimitri van Heesch | 2019-12-26 | 1 | -3498/+3428 |
|\ | |||||
| * | issue #7446: C#: parameter named `extends` is broken in the documentation | Dimitri van Heesch | 2019-12-20 | 1 | -4/+4 |
| | | |||||
| * | Incorrect warning "yyextra->inside" instead of "inside" | albert-github | 2019-12-18 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | | | | We get warnings like: ``` warning: reached end of file while yyextra->inside a 'code' block! warning: Ignoring \brief command yyextra->inside argument documentation ``` this is due to the fact that the scanner has been made reentrant (inside becomes yyextra->inside and this slipped into the warning strings as well) | ||||
| * | issue #7412: HTML: Opening a reference link in a new tab does not scroll to ↵ | Dimitri van Heesch | 2019-12-10 | 1 | -2/+5 |
| | | | | | | | | the content | ||||
| * | Merge branch 'master' into feature/bug_coverity_unint | Dimitri van Heesch | 2019-12-08 | 1 | -85/+58 |
| |\ | |||||
| | * | Changed std::unique_ptr<Entry> to std::shared_ptr<Entry> at avoid use after ↵ | Dimitri van Heesch | 2019-12-08 | 1 | -45/+46 |
| | | | | | | | | | | | | free issues | ||||
| | * | Added missing debug flags for scanner that were made reentrant | Dimitri van Heesch | 2019-12-05 | 1 | -0/+3 |
| | | | |||||
| | * | Split language parser into "outline parser" and "code parser" | Dimitri van Heesch | 2019-12-03 | 1 | -40/+9 |
| | | | |||||
| * | | Coverity uninitialized | albert-github | 2019-12-02 | 1 | -1/+1 |
| |/ | | | | | | | Fixing a number of uninitialized variables based on the coverity output of November 30, 2019 | ||||
| * | Made scanner.l reentrant | Dimitri van Heesch | 2019-12-01 | 1 | -3329/+3371 |
| | | |||||
| * | Fixed line count misaligned introduced with JAVADOC_BANNER | Dimitri van Heesch | 2019-11-24 | 1 | -36/+38 |
| | | |||||
| * | Cleanup scanner.l code and naming | Dimitri van Heesch | 2019-11-24 | 1 | -2756/+2723 |
| | | |||||
| * | Made code.l scanner reentrant | Dimitri van Heesch | 2019-11-21 | 1 | -2/+5 |
| | | |||||
| * | Remove bogus flex code | Dimitri van Heesch | 2019-11-18 | 1 | -7/+0 |
| | | |||||
| * | Fix line count after multiline close group | Roel Standaert | 2019-11-12 | 1 | -0/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | Fix for issue #7393 When closing a group on multiple lines, like: /*! @} */ The line count of subsequent lines is wrong (it's one line less than it should be). | ||||
| * | Simplied the logic for moving documentation to the most nested Entry | Dimitri van Heesch | 2019-11-10 | 1 | -23/+21 |
| | | |||||
| * | Merge branch 'feature/issue_7295' of ↵ | Dimitri van Heesch | 2019-11-10 | 1 | -0/+17 |
| |\ | | | | | | | | | | https://github.com/albert-github/doxygen into albert-github-feature/issue_7295 | ||||
| | * | issue #7295 Doxygen documentation of C++17 nested namespace erroneous | albert-github | 2019-10-06 | 1 | -0/+17 |
| | | | | | | | | | | | | documentation has to be added to the "last" entry not to the "first" / "top" |