Step inside our office and see how we tackle complex engineering challenges at our company. In this video, we take you through the journey of creating the massive PHPCPD 8.3.0 update – from initial whiteboard brainstorming in our conference room to the final technical implementation.
Get a look at our internal process and how we approached a fundamental architectural shift in code clone detection. Our team implemented the “Barrier Token” method – a crucial solution designed to ensure surgical precision in analysis and provide native support for the #[SuppressCpd] attribute.
In this video, we share how our team implemented this new workflow:
🔹 Pre-Filtering Engine: How we transform raw PHP code into a token stream and inject special “Barrier Tokens” (unique strings) to create hard boundaries between different contexts.
🛡️ Native #[SuppressCpd] Support: How the engine recognizes developer intent, turning ignored code blocks into architectural “walls” at an early stage.
⚙️ Dual Strategy Analysis: How we forced our two main detection strategies to interact with these new barriers:
- Default Strategy (Rabin-Karp Hashing): How hashing instantly interrupts upon collision with a barrier.
- Suffix Tree Strategy (Graph Analysis): How the barrier token becomes a “Dead End Node”, immediately stopping graph construction.
This video is for engineers and developers interested not just in what we built, but how we built it.