dbForEach dbForAll and db*Next* difference

I also found there are dbIterAllRoutes ,dbIterRoutes ,dbEndIterRoutes,dbEndIterAllRoutes,so I think dbNext* are used in this iteration method, such as the following code :

set iter [dbIterRoutes $net]
while {[set route [dbRouteNext $iter]] != "0x0"} {
if [dbIsRouteWire $route] {
set wire_info [dbInfoWire $route]
} elseif [dbIsRouteVia $route] {
set via_info [dbInfoVia $route]
} else {
puts "something’s wrong\n"
}
...
if (want to break out of the iterator loop)
dbEndIterRoutes $iter
...
}

 But I'm wondering why  cadence add this new iteration method,  and what's difference between dbIterRoutes and dbIterAllRoutes? Thanks!

I seem to these commands being necessary when there wasn't a data-type-specifc dbForEach* iterator command available.  The dbForAll (as opposed to dbForEach) seemed to be necessary when you wanted to iteration through, for example, power pins in addition to signal pins when iterating through pins on a cell.

However, you should be able to get at this information with the dbGet command that debuted in 7.1.  Are you seeing some cases where you still need to use these old style commands?  If so let us know so we can improve dbGet and/or help with usage of some of these more confusing old style commands.

Thanks,
Bob

Hi Bob,

Thanks for your reply, I think Encounter have design to have many commands, it have very powerful and flexible command to let use to investigate and operate database, But it's not easy for user to find the exact command to implement user's intent, I think dbGet,dbSet is more easy to let user get some attribute since it's structured and more organized. anyway it will need  time to be expert in encounter