Vibe's chip design tool deleted two handwritten Verilog parsers that used regular expressions to inspect a chip's pad ring, the circuit around the edge that connects internal logic to package pins. The tool now asks Yosys and Slang, established Verilog front ends, to read the selected models with their real definitions and include directories.
That difference shows up when source files depend on one another. Cross-file macros now resolve as one compiled unit, active preprocessor branches decide which ports exist, and configured models take priority over files a simple scanner happened to find. The paired comparison against version 0.4.92 reported no newly failed designs.
Hardware languages are too contextual for a collection of regular expressions to remain correct as projects grow. Tool builders should keep custom code for the question they are answering and delegate language parsing to a maintained front end. The extra dependency costs less than debugging a pad connection that vanished because a scanner read the wrong branch.