Tags » Code Analysis

What do "parsing" and "resolving" mean anyway?

In Rubberduck 1.x, we processed each module in each project sequentially. Rubberduck 2.0 will change that and have the parsing happen in parallel, asynchronously… 1,470 more words


Installing SonarQube on Ubuntu

credits go to Anna Bansaghi for the how-to found here:


– Java JRE
– DBMS (MySQL for example, but works like a charm with PostgreSQL aswell) 386 more words


You've waited long enough.

The wait is over!

I have to say that this release has been… exhausting. Correctly resolving identifier references has proven to be much, much more complicated than I had originally anticipated. 693 more words


Analyze Python cProfile stats created with pstats.dump_stats() off line.


In order to improve Code Performance, I need to find functions that are good candidates for Cython implementation.

Here’s the link to the Python Docs for Code Profiling. 301 more words


Preventing bugs, and improving code quality with Microsoft SAL (Part 2, custom preconditions for structs & objects)

Note: At the end of part 1, I’d suggested that part 2 would be about invalid handles. This post however isn’t about invalid handles. That’ll be the next part in this series. 1,769 more words

Featured Posts

Rubberduck 1.3: When the VBE becomes a real IDE

Parsing is hard!

Rubberduck parsing is being refined again. The first few releases used a hand-made, regex-based parser. That was not only unmaintainable and crippled with bugs, it also had fairly limited capabilities – sure we could locate procedures, variables, parameters… but the task was daunting and, honestly, unachievable. 456 more words


Signal-Slot diagram using Doxygen and XSLT

Qt signal-slot analysis using Doxygen and XSLT

Sometimes I need to see connections between signals and slots in my Qt projects. It seems like now there is no software than can do this. 3,316 more words

Без рубрики