Stats

  • Locked Locked
  • Replies 2
  • Subscribers 142
  • Views 1289
  • 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

Standard I/O Ports Not Available in SKILL++ by Default

AaronSymko

Standard I/O ports (with the exception of poport) are not available in SKILL++ by default. It requires an importSkillVar to make them visible. Is this an oversight, or is there a good reason why this is so?

For example:

toplevel 'ils
poport
port:"*stdout*"
woport
*Error* eval: unbound variable - woport
importSkillVar woport
t
woport
port:"*ciwWarnPort*"

Parents

  • I think they were not shared between the two namespaces by default (I am not even sure about poport, are you sure it's not any script in your setup that made the import?)

    I believe using importSkillVar as you do to make them global in SKILL++ is not really risky

    Anyway, on my side I created specific functions using inSkill to make sure I do not overlap any specific name (get_woport, set_woport, etc.)

Reply

  • I think they were not shared between the two namespaces by default (I am not even sure about poport, are you sure it's not any script in your setup that made the import?)

    I believe using importSkillVar as you do to make them global in SKILL++ is not really risky

    Anyway, on my side I created specific functions using inSkill to make sure I do not overlap any specific name (get_woport, set_woport, etc.)

Children
  • in reply to AurelBuche

    poport and piport are imported automatically into SKILL++ as a small set of "required" global variables. This has been this way for a very long time (I didn't go back to check when - as far as I can see it's always been this way). I don't think it's an oversight to not include the others, but just done because you frequently would need at least some port to write to and read from.

    Andrew

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.