Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 855
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Info on "oblist"

Sutlieff

Hi all,

I am debugging some internal legacy SKILL and have come across some code that is using "oblist"

It seems that this is some internal Cadence list (when trying to change it  I am getting:  "*WARNING* (Parser): oblist is a reserved name and cannot be assigned to"

This list, for one particular user, is extremely large so I am curious how this list gets generated.

I am searching for a pop-up window id so I thought I would use hiFormList instead of oblist.

Can anyone shed a bit more light on this list and how it is generated?

Thanks

Colin

Parents
  • Andrew Beckett

    Hi Colin,

    Code should not use oblist. It's a representation of the contents of SKILL's symbol table - so any time a symbol is created (for a function, a variable, a property, any time that name is used) it ends up in oblast. Because of this, it can't be assigned to because it isn't actually the symbol table.

    If the symbol table gets very large, it could be an indication that there is some SKILL code that is creating pseudo-arrays using variables (rather than using true arrays or hash tables). it's big anyway, but if it's especially big for one user, there may be some customisation doing something bad. Because it can be pretty large, searching it as a list is a bad idea, so your suggestion of using hiFormList is a better idea.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Hi Colin,

    Code should not use oblist. It's a representation of the contents of SKILL's symbol table - so any time a symbol is created (for a function, a variable, a property, any time that name is used) it ends up in oblast. Because of this, it can't be assigned to because it isn't actually the symbol table.

    If the symbol table gets very large, it could be an indication that there is some SKILL code that is creating pseudo-arrays using variables (rather than using true arrays or hash tables). it's big anyway, but if it's especially big for one user, there may be some customisation doing something bad. Because it can be pretty large, searching it as a list is a bad idea, so your suggestion of using hiFormList is a better idea.

    Regards,

    Andrew.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.