On Apr 22, 10:22 am, Marc Heise <mhe...@[EMAIL PROTECTED]
> wrote:
> Riad KACED wrote:
> > Ahmad,
>
> > I'm not really sure about it but my attempt is :
> > A symbol is graphical interface to a design data.
> > The symbol is generally a black box (even it has other shapes ...)
> > that holds a given data and offers a set of pi/properties to interface
> > with the external world.
> > The design data could be :
> > 1. A spice model for example. The "nmos" symbol from your CDS
> > analogLib can call a BSIM3 model, a CDL model and stuff ...
> > 2. A piece of design or sub-design you pack into a box to make it
> > easier to include in a hierarchy. The sub-design itself could be made
> > by other symbils/primitives, ASCII file, like a verilog/VHDL/DSPF ....
> > etc.
>
> > Wow, It's not an easy question actually, Hope I was not rubbish in my
> > explanation ;-)
>
> > Well I would say that a symbol for a design data is what the body is
> > for a car. I know... I'm not good in poesy either ...
> > Hope other folks will help, I'm afraid y're going any further with my
> > explanation ...
>
> > God luck anyway !
>
> > Riad.
>
> You misunderstood him. He was asking for the do***entation:
>
> SKILL Language User Guide, Chapter 4 "Data Structures"
>
> Regards,
> Marc
Thank you all, but I exactly mean Marc's answer :)
Thank you Riad .. You're perfect anyway
Regards
Ahmad
|
