RE: Model name question

You know, you could just put one component per file. That's what I do, for
exactly the reason you mention.

Todd.

Todd Westerhoff
SI Engineer
Hammerhead Networks
5 Federal Street
Billerica, MA 01821
twester@hhnetwk.com
ph: 978-671-5084

-----Original Message-----
From: Al Davis [mailto:aldavis@ieee.org]
Sent: Monday, July 16, 2001 4:42 PM
To: Scott McMorrow; Lynne Green
Cc: Muranyi, Arpad; 'ibis@eda.org'
Subject: Re: Model name question

On Monday 16 July 2001 11:14 am, Scott McMorrow wrote:
> Lynne,
>
> My suggestion is to formalize the concept that a unique model name
> is described by the following:
>
> manufacturer.component.model.revision.

That doesn't work. Model is not in Component scope. Model and
Component are at the same level as far as scoping is concerned.

You can have a file ...

[Component]
[Component]
[Component]
[Model]
[Model]
[Component]

etc...

All models are available to all components in that file.

The only scoping we have is by file.

Moving forward, it may make sense to introduce a [Namespace] to deal
with these scoping issues, but I don't think this will solve the
problem either.

Should IBIS-X offer nested [Define]s ??

al.

 
Received on Tue Jul 17 05:32:18 2001