Re^2: Problem with storing values (Verilog::Netlist::Net)

Thank you very much for your reply. Well, the reason I was trying to do this is I'm trying to reuse bits of code that one of my seniors wrote for something similar. It appears that the source code of "dump_drivers" has changed since he used it(a few years back). I tried your method using select, it does seem to work for now. Could you explain what exactly did you do there? The thing is, this is much easier for me to write code for the pins like this as I am cycling through all the pins in the design like so:

foreach my $cell ($mod->cells) {
     foreach my $pin ($cell->pins) {
          $netdrivers = ($pin->net)->dump_drivers;


     }
}
[download]

Then I'm using the drivers to check some conditions. Maybe I could store all the pin drivers for the design beforehand and look them up when required, but this is just so convenient. Is the only reason you would now recomment obtaining the values from STDOUT be that the functionality of "dump_drivers" could change again at anytime? Or is there some other reason? Thanks!

Comment on Re^2: Problem with storing values (Verilog::Netlist::Net) Download Code

Replies are listed 'Best First'.
Re^3: Problem with storing values (Verilog::Netlist::Net) by toolic (Bishop) on Apr 16, 2015 at 20:21 UTC
You're welcome. Yes, as I stated, I don't think you should use the dump_drivers output. The primary reason is that it can change in future versions of Verilog-Perl without notice. The module author provides some support at http://www.veripool.org/projects/verilog-perl/boards	[reply]