Subject: RE: [sv-ec] Err-5
From: David W. Smith (David.Smith@synopsys.com)
Date: Thu Nov 20 2003 - 16:12:11 PST
Greetings,
So, the process to resolve this is that when it is discussed at the meeting
(Monday) a motion can be made to modify the proposal to name the package
(pick a name, I personally like fred but std is probably more meaningful).
One other comment. The correct term for the scope at the top of the
compilation unit is the compilation-unit scope as defined in Section 18. We
should try to use this and "compilation unit" (instead of unit of
compilation) consistently since they are presented as specific defined terms
in Section 18.2.
Regards
David
-----Original Message-----
From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Arturo
Salz
Sent: Tuesday, November 18, 2003 9:23 PM
To: Warmke, Doug; 'Arturo Salz'; Ryan, Ray; 'sv-ec@server.eda.org'
Subject: Re: [sv-ec] Err-5
Doug,
You are correct about C++ being in a state of transition and std:: being the
new namespace where standard utilities reside.
As I wrote in my earlier message, a named package is a plausible
alternative.
I have nothing against such an approach. The current proposal takes a
slightly
different approach, one that has been in use for some time.
Arturo
----- Original Message -----
From: "Warmke, Doug" <doug_warmke@mentorg.com>
To: "'Arturo Salz'" <Arturo.Salz@synopsys.COM>; "Ryan, Ray"
<Ray_Ryan@mentor.com>;
"'sv-ec@server.eda.org'" <sv-ec@eda.org>
Sent: Tuesday, November 18, 2003 8:25 PM
Subject: RE: [sv-ec] Err-5
Ray wrote:
I'd prefer the built-in package to have a name (rather than 'he who shall
not
be named'). This is just a preference - there is nothing technically wrong
with the null name.
Arturo wrote back:
That is a plausible way to define it. However, that would be
incompatible with
other mainstream languages such as C++ and Java. Plus, the committee did
approve this form.
Doug writes:
Arturo, this isn't strictly true with C++.
Right now the language is in transition.
It is possible to use types defined in the "std" library
(aka STL) without qualification, but that is deprecated.
Consider the STL class "vector". In the future,
it will be necessary to qualify all references to a type
such as vector. One can either refer to the type with a
fully qualified name, such as "std::vector", or one can
employ "using" syntax to import the visibility of
"vector" from the "std" (dare I say it? package!)
into the current scope.
As I mentioned in the SV-BC meeting (and I did hear the groans!),
I don't see what is wrong with naming the built-in namespace "std".
It has precedent in both C++ and VHDL. That could connote a lot
to SystemVerilog users.
I will be interested to hear details of why you think this proposal is
incompatible with C++. (I don't know much about Java, unfortunately).
Regards,
Doug
This archive was generated by hypermail 2b28 : Thu Nov 20 2003 - 16:13:41 PST