Menu

1 / 2

Firing Doxygen: Native Parser Architecture and Adopting libclang

DEV Community: cpp·Flude team·20 days ago
#b1wj2D26
#devtocpp#devto#dev#parser#doxygen
Reading 0:00
15s threshold

Doxygen had been with us since day one. At the MVP stage, it was a conscious and absolutely correct choice: it allowed us not to write a C++ parser from scratch, but to immediately focus on business logic and documentation rendering.

But as we transitioned from local scripts to a cloud SaaS, Doxygen turned into a burden. It couldn't cache the AST, its binary was too bulky, and its internal parser broke from C++ templates (remember the SFINAE incident from the previous episode , which forced us to write crutches via INPUT_FILTER ).

It was time to do what we planned from the very beginning: fire Doxygen and migrate the system to native parsers.

Divide and Conquer

We never harbored illusions about creating a "universal parser". Just like with Doxygen dialects, we initially designed the system for separate parsers for each language.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.