Meeting Reminder, Agenda, Minutes and Proposals


Subject: Meeting Reminder, Agenda, Minutes and Proposals
From: Bailey, Brian (brian_bailey@mentorg.com)
Date: Tue Oct 07 2003 - 13:27:20 PDT


Hi Everyone,
    This email contains quite a few pieces, so please make sure that you check them all out. Our next meeting is on Thursday 9th at 9:00am Pacific time. Call in details are on the web. Attached are the minutes from the previous meeting.

The agenda for this meeting contains the following items:
Public meeting planning
Invitation letter
Establish new sub-groups
Proposals from Zaiq
Nominations for new ITC co-chair

 MI 01 modified

  The C++ and C APIs shall be defined in a header file with the name

    scemi.h

  Note, name is all-lowercase.

  It is up to the implementation whether there are two distinct header
  files for C++ and C APIs or one merged file. When there are two
  distinct files, they must have the same name (hence they will appear
  in separate directories).

  Usage note for C++:

    #include <cstdlib>
    #include <scemi.h>

    int
    main(int argc, char *argv[])
    {
      SceMiParameters *parms = new SceMiParameters("ParameterFile");
      SceMi *sceMi = SceMi::Init(SCEMI_VERSION_STRING, parms);

      // etc.
    }

  Usage note for C:

    #include <stdlib.h>
    #include <scemi.h>

    int
    main(int argc, char *argv[])
    {
      SceMiParameters *parms = SceMiParametersNew("ParameterFile");
      SceMi *sceMi = SceMiInit(SCEMI_VERSION_STRING, parms);

      // etc.
    }

Additionally, I thought of the following which we did not discuss but
that I would like to amend to the proposal:

  An implementation is free to introduce other implementation-specific
  include files. However, any filename matching the shell glob scemi*.h
  is reserved for future use by SCE-MI.

 MI 03 - The prefixen `SceMi', 'scemi', `sceMi', 'Sce_Mi', 'sce_Mi', and
     `sce_mi', as well as all other possible capitalizations of these
     as used in C++ and C identifiers are reserved for use by SCE-MI.
     An implementation may not use this prefix for any
     implementation-specific purpose.

 MI 04 - The C++ API should define a namespace for the SCE-API definitions.
     In a transition period, the SCE-API header should include a using
     directive for this namespace to allow compilation of existing code
     without modification. However, new code is encouraged to not rely
     on this. I propose the namespace to be named SceMi:

       namespace SceMi
       {
         class SceMi
         {
         public:
           Init(int Version,
                SceMiParameters *parameters,
                SceMiEC *ec = NULL);

           // etc.
         }

         // More definitions here.
       }

       // During the transition phase add this to scemi.h:
       using namespace SceMi;

       // This is optional in user code:
       using namespace SceMi;

       // After the transition period, if the user code did not get
       // changed to include the using directive above:

       SceMi *sceMi; // Error: SceMi not in global namespace
       SceMi::SceMi *sceMi; // Ok: Explicit reference to SceMi namespace

 <<Minutes250903.doc>>

==============================================
Brian Bailey brian_bailey@mentor.com
Chief Technologist Tel: 503 685 1371
Design Verification and Test Division Fax: 503 685 1652
Mentor Graphics Corp. 8005 S.W. Boeckman Rd. Wilsonville, OR 97070




This archive was generated by hypermail 2b28 : Tue Oct 07 2003 - 13:27:56 PDT