3 Reasons Why Verification Engineers should use Python instead of Perl
December 8, 2015
After many years of writing design verification automation scripts in Perl, we at Arrow Devices made a conscious decision to shift to Python, lock, stock and barrel. Scripting in Perl has multiple problems and so we started looking for an alternative. We looked at multiple options but finally zeroed in on Python. Here is why:
Related Semiconductor IP
- nQrux® Root of Trust IP
- AXI to UCIe Bridge IP
- UCIe 2.x Controller IP
- SWI3S (SoundWire I3S Interface) Peripheral Controller Core IP
- OpenTitan-based RISC-V Secure Element
Related Blogs
- Top 3 Reasons Why Design IP Is Business Friendly
- Why Codasip Cares About Processor Verification - and Why you Should too
- FiRa 3.0 Use Cases: Expanding the Future of UWB Technology
- 3 Reasons That the Semiconductor Clouds Are Gathering
Latest Blogs
- From Bug Hunting to Engineering Methodology: Lessons from AI-Driven Development
- Manufacturing Intelligence: Turning EDA Data into Trusted Action
- Execute-in-Place: Getting More from Embedded NVM
- Rethinking RTL flows with AI-driven hybrid formal verification
- Arm and NVIDIA: Building the trusted compute foundation for the agentic AI era