Re: PTF meeting minutes for 1/12/2004

From: Shalom Bresticker (Shalom.Bresticker@motorola.com)
Date: Thu Jan 15 2004 - 04:01:18 PST

  • Next message: chas@cadence.com: "errata/530: 26.6.17 expr class does not contain vpiTchkTerm - should model different"

    I understand.

    Thanks,
    Shalom

    Stuart Sutherland wrote:

    > Shalom,
    >
    > The names in the diagram are correct. The space is a critical part of the
    > object name. The C constant in the vpi_user.h file (Annex G) is built from
    > the object name, by prepending the letters "vpi" and capitalizing the first
    > letter of each word in the object name. Thus, the object "def param" is
    > represented by the constant "vpiDefParam". These naming conventions are
    > covered in Section 26.3, and are well known to all programmers that work
    > with the VPI. Because C is case sensitive, the object in the diagram cannot
    > be called "defparam". That would result in users of the diagrams trying to
    > use a constant "vpiDefparam" which does not exist in the VPI library.
    >
    > I agree that way back in 1996 or so when we first defined the vpi_user.h
    > file, it would have been better to have kept the object names the same as
    > the Verilog keywords wherever possible. It is too late to change the case
    > of some constant names in the header file now, however. That would wreak
    > havoc on exiting user and commercial applications.
    >
    > Stu
    >
    > ~~~~~~~~~~~~~~~~~~~~~~~~~
    > Stuart Sutherland
    > stuart@sutherland-hdl.com
    > 503-692-0898
    >
    > > -----Original Message-----
    > > From: owner-ptf@boyd.com [mailto:owner-ptf@boyd.com] On
    > > Behalf Of Shalom.Bresticker@motorola.com
    > > Sent: Tuesday, January 13, 2004 11:27 PM
    > > To: PTF
    > > Subject: Re: PTF meeting minutes for 1/12/2004
    > >
    > > Please clarify.
    > > The only such references are 26.6.1, 12, 42.
    > > Everywhere else in the standard, they are called defparam's
    > > and specparam's, though specparams's are sometimes called
    > > 'specify parameters', I think, but never 'spec params'.
    > >
    > > There are no such entities in the LRM as 'def params' and
    > > 'spec params'.
    > >
    > > > - Shalom's request to change "def param" to "defparam" and
    > > > "spec param" to "specparam".
    > > >
    > > > Discussed. Diagrams are correct as is. Are there other
    > > > references? Chas to touch base with Shalom on this issue.
    > >
    > > Thanks,
    > > Shalom
    > >
    > > --
    > > Shalom Bresticker
    > > Shalom.Bresticker@motorola.com
    > > Design, Verification & Reuse Methodology Tel:
    > > +972 9 9522268
    > > Motorola Semiconductor Israel, Ltd. Fax:
    > > +972 9 9522890
    > > POB 2208, Herzlia 46120, ISRAEL Cell:
    > > +972 50 441478
    > >
    > >
    > > 

    --
Shalom Bresticker                           Shalom.Bresticker@motorola.com
Design & Reuse Methodology                             Tel: +972 9 9522268
Motorola Semiconductor Israel, Ltd.                    Fax: +972 9 9522890
POB 2208, Herzlia 46120, ISRAEL                       Cell: +972 50 441478

    This archive was generated by hypermail 2.1.4 : Thu Jan 15 2004 - 03:50:04 PST and
    sponsored by Boyd Technology, Inc.