• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. create a table inside the class

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 14562
  • 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

create a table inside the class

skillseeker
skillseeker over 12 years ago

Hi,

I would like to create a table for each instance of a class. How best to do it. If i define "makeTable" inside a defclass it gives me an error.

 defclass( pinInfo
    ()
    (
     ( pinName   @initarg pinName )
     ( pinType   @initarg pinType )
     ( netName   @initarg netName )

     PinTable = makeTable("aTable1" 0)

     tablep(PinTable)
    )

  );defclass

I get an error when i define it like this "*Error* slotValue: no such slot - PinTable.

Thanks

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    You can't just stick arbitrary code inside a class definition - you could either do it with an @initform:

    defclass(pinInfo
      ()
       (
        (pinName @initarg pinName)
        (pinType @initarg pinType)
        (netName @initarg netName)
        (pinTable @initform makeTable("aTable1" 0))
       )
    )

    Then:

    > a=makeInstance('pinInfo)
    stdobj@0x8564018
    > a->pinTable
    table:aTable1
    > a->pinTable["hello"]=23
    23
    > a->pinTable->??
    ("hello" 23)

    Or you could define an initializeInstance method:

    defclass(pinInfo
      ()
       (
        (pinName @initarg pinName)
        (pinType @initarg pinType)
        (netName @initarg netName)
        (pinTable)
       )
    )

    defmethod(initializeInstance @after ((obj pinInfo))
      obj->pinTable=makeTable("aTable1" 0)
    )

    Note that the second approach only works in IC615 onwards. You could use a non-@after method, but then you'd have to make sure you call callNextMethod() appropriately to ensure that any parent objects have a chance to initialize too. The @after directive tells it to call all the other @after methods, least-specific first.The intention for initializeInstance is to handle complex initialization of objects which can't be coded via the @initform (e.g. interdependencies of the arguments).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    You can't just stick arbitrary code inside a class definition - you could either do it with an @initform:

    defclass(pinInfo
      ()
       (
        (pinName @initarg pinName)
        (pinType @initarg pinType)
        (netName @initarg netName)
        (pinTable @initform makeTable("aTable1" 0))
       )
    )

    Then:

    > a=makeInstance('pinInfo)
    stdobj@0x8564018
    > a->pinTable
    table:aTable1
    > a->pinTable["hello"]=23
    23
    > a->pinTable->??
    ("hello" 23)

    Or you could define an initializeInstance method:

    defclass(pinInfo
      ()
       (
        (pinName @initarg pinName)
        (pinType @initarg pinType)
        (netName @initarg netName)
        (pinTable)
       )
    )

    defmethod(initializeInstance @after ((obj pinInfo))
      obj->pinTable=makeTable("aTable1" 0)
    )

    Note that the second approach only works in IC615 onwards. You could use a non-@after method, but then you'd have to make sure you call callNextMethod() appropriately to ensure that any parent objects have a chance to initialize too. The @after directive tells it to call all the other @after methods, least-specific first.The intention for initializeInstance is to handle complex initialization of objects which can't be coded via the @initform (e.g. interdependencies of the arguments).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information