Subject: Re: [sv-cc] Header file names?
From: Michael Rohleder (michael.rohleder@motorola.com)
Date: Mon Mar 10 2003 - 02:16:10 PST
IMHO, this very much depends on how we want to handle the other extensions:
- do we want to have a vpi extension header for coverage (e.g. vpi_coverage.h) and a second one for assertions (vpi_assert.h); or
do we want a SystemVerilog specifc VPI extension header (sv_vpiext.h).
- when the svc.h and svc_src.h are covering only DPI, then the names 'dpi.h' and dpi_src.h' might be more descriptive.
But I also like svdpi.h and svdpi_src.h, this gives some better link to SystemVerilog specifics.
- If these files are also covering the VPI extensions (which they currently don't), then svc.h, svc_src.h might be better.
In general, my answer is X (don't care).
-Michael
Bassam Tabbara wrote:
> How about svdpi_... ?
>
> > -----Original Message-----
> > From: owner-sv-cc@server.eda.org
> > [mailto:owner-sv-cc@server.eda.org] On Behalf Of Warmke, Doug
> > Sent: Friday, March 07, 2003 9:31 PM
> > To: 'sv-cc@server.eda.org'
> > Subject: [sv-cc] Header file names?
> >
> >
> > Team,
> >
> > It appears as if we are renaming "DirectC" to "DPI"
> > (Direct Programming Interface).
> >
> > Does it make sense at this time to rename our
> > two header files?
> >
> > svc.h -> dpi.h
> > svc_src.h -> dpi_src.h
> >
> > Opinions welcome.
> >
> > Regards,
> > Doug
> >
--NOTE: The content of this message may contain personal views which are not neccessarily the views of Motorola, unless specifically stated.
___________________________________________________ | | _ | Michael Rohleder Tel: +49-89-92103-259 | _ / )| Software Technologist Fax: +49-89-92103-680 |( \ / / | Motorola, Semiconductor Products, System Design | \ \ _( (_ | _ Schatzbogen 7, D-81829 Munich, Germany _ | _) )_ (((\ \>|_/ > < \_|</ /))) (\\\\ \_/ / mailto:Michael.Rohleder@motorola.com \ \_/ ////) \ /_______________________________________________\ / \ _/ \_ / / / \ \
The information contained in this email has been classified as: Motorola General Business Information (x) Motorola Internal Use Only ( ) Motorola Confidential Proprietary ( )
*** This note may contain Motorola Confidential Proprietary or Motorola Internal Use Only Information and is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. Thank you! ***
This archive was generated by hypermail 2b28 : Mon Mar 10 2003 - 02:18:28 PST