Stats

  • Locked Locked
  • Replies 2
  • Subscribers 144
  • Views 727
  • 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

Skill++ - create another class that is composed of two instances from another class

rflayout

I've created a class that is supposed to represent a two-dimensional point. It is defined here:

 defclass( gf_2dPoint

   () ;superclass

   (

      (x

         @initarg x

         @reader getX

         @writer setX

      )

      (y

         @initarg y

         @reader getY

         @writer setY

      )

   )

) ; defclass

Then in my main procedure I instantiate two points like so:
   gf_Pt1 = makeInstance('gf_2dPoint ?x 0 ?y 3)
   gf_Pt2 = makeInstance('gf_2dPoint ?x 2 ?y 5)
 
I wanted to create another class, maybe called gf_line, whereby a gf_line instance could be created with the makeInstance and passing to gf_2dPoint objects.
 
Thanks for any insights.
By the way, I may just use a simpler procedure solution, but was a bit curious.
-Gary 
Parents
  • Andrew Beckett

    Gary,

    I think you've answered your own question. Probably you'd just use:

    defclass(gf_line ()
      (
        (pt1 @initarg pt1 @reader getPt1 @writer setPt1)
        (pt2 @initarg pt2 @reader getPt2 @writer setPt2)
      )
    )

    gf_l1=makeInstance('gf_line ?pt1 gf_Pt1 ?pt2 gf_Pt2)

    It wouldn't make much sense to use inheritance here - since a line is not a special type of a point.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Gary,

    I think you've answered your own question. Probably you'd just use:

    defclass(gf_line ()
      (
        (pt1 @initarg pt1 @reader getPt1 @writer setPt1)
        (pt2 @initarg pt2 @reader getPt2 @writer setPt2)
      )
    )

    gf_l1=makeInstance('gf_line ?pt1 gf_Pt1 ?pt2 gf_Pt2)

    It wouldn't make much sense to use inheritance here - since a line is not a special type of a point.

    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.