RSpice now treats Verilog, Verilog-A, and Verilog-AMS, the related languages used to describe digital, analog, and mixed-signal circuits, as project-owned cell views. Creating one seeds a module from the cell's ports, compiles it before RSpice keeps it, and generates the symbol that a schematic can place. That closes a practical gap between writing a circuit model and making it usable by the rest of a design.
The change touches 41 files because a source view has to survive more than an editor tab. RSpice stops hierarchy traversal at the view, binds it into the generated simulator input, tracks whether its symbol is stale, and loads a digital Verilog module onto the event simulator. The accompanying tests exercise creation, compilation, netlisting, events, and waveforms.
This is the useful shape of code-native electronic design automation: a text file becomes a checked design object without an engineer copying module names and port lists into separate dialogs. Teams evaluating RSpice should try one mixed-signal block with a changing port list and check whether the generated symbol stays synchronized through review and simulation.