Re: [sv-cc] Updated extern/exports proposal

Subject: Re: [sv-cc] Updated extern/exports proposal
From: Michael Rohleder (michael.rohleder@motorola.com)
Date: Wed Mar 12 2003 - 09:04:37 PST

Only minor comments on this:

a) I think we need to get our BNF fixed. cname and fname are symbols and should be qualified as such (<cname>, <fname>), while pure and context are literals.

b) First paragraph after Semantics. Change the sentence starting with "An error ..." to "An error will be generated iff the <cname> (or the <fname> in case the <cname> is omitted) has characters that are ...)"

c) Second paragraph after Semantics: I would suggest to prepend the sentence:
"The above syntax permits to map multiple SV functions to map to the same foreign language function by supplying the same <cname>."
I also think that the type signature should include the direction of a formal param.

d) Third paragraph after Semantics:
 . avoid 1, say 'one'
 . the bracket '(extern or export)' is confusing. This sounds like a fname can have both ??? What is the intention of this?
 . " ... where the "export" occurs ..."; better say " ... where the exported SV function is located ... "
 . The note must also require matching default values; this is not required elsewhere ...
 . The first half of paragraph 6 is a repetition of the middle of paragraph 3, isn't it?

e) Description of pure:
 . would not say 'reads' data; suggest to use 'uses data'
 . the function output is the function result only, this should be clearly stated
 . it should clearly say that pure functions must not have inout or output params

f) Description of context:
It is the users responsibility to create, manage or otherwise manipulate the required handles/environment(s) needed by the other interfaces.
 

-Michael
 

Joao Geada wrote:

Attached as an HTML file.
I believe I have accounted for all the required clarifications and corrections.
There is now a lot more detail about the behavior of  pure and context functions,
description of the context manipulation APIs, examples of context, descriptions
of the capabilities and limitations of extern and exported functions, listing
of issues that are deferred with current "workarounds".
In addition, I have also permitted multiple externs to exist in 1 scope IFF
all the externs define exactly the same type signature and all agree exactly
on the names of formals (as requested by Michael). Note that in addition, the
workaround section suggests a few better ways to address this issue.

Joao
==============================================================================
Joao Geada, PhD             Principal Engineer                Verif Tech Group
Synopsys, Inc                                              TEL: (508) 263-8083
344 Simarano Drive, Suite 300,                             FAX: (508) 263-8069
Marlboro, MA 01752, USA
==============================================================================

  ------------------------------------------------------------------------------------------------------------------------------------
                                        Name: Updated externexport proposal.htm
   Updated externexport proposal.htm    Type: Hypertext Markup Language (text/html)
                                    Encoding: quoted-printable

--

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 : Wed Mar 12 2003 - 09:09:25 PST