If there is no access to individual
characters of a string, we do not need to define the type of the individual
character. As we have said that we do not support the string methods (IEEE
1800-2005, 4.7.1-15) there is no issue with these methods. Then considering
the operators in 1800-2005, Table 4-2: if we decide not to support the
indexing operation, all possible references/acces methods to bytes from
1800-2005 are absent and you leave out the refence to the byte type when
copying the SV text.
Alternatively, if the indexing operator
is considered too useful to leave out, we can restrict the interpretation
of the byte data type to an ASCII value as defined in 1800-2005, Table
4-1 (so not as 2-value SystemVerilog value, nor as 8-bit signed integer,
only as ASCII character). However, in my opinion this can better wait until
we move to SV-AMS and accept the full package for string and byte types
in AMS.
Cheers,
Marq
Marq Kole
Domain Leader Robust Design
Research
NXP Semiconductors
Tel: +31 40 27 49051, Fax: +31 40 27 46276, Mobile: +31 6 387 48 389
High Tech Campus HTC-37.4.037, 5656 AE Eindhoven, The Netherlands
marq.kole@nxp.com, www.nxp.com
"Geoffrey.Coram" <Geoffrey.Coram@analog.com>
Sent by:
owner-verilog-ams@server.eda.org
20-04-2007 16:04
To
verilog-ams <verilog-ams@server.eda-stds.org>
cc
Subject
Re: minutes Verilog-AMS Committee Meeting
- 19 April 2007
Classification
Marq Kole wrote:
>
> Geoffrey will update section 3 (merged_datatype) with the
> string variable as discussed in the review of section 11.
I think it was the review of section 10, system tasks.
I'm struggling with the SV text, which makes lots of references to the
"byte" datatype, eg,
A single character of a string variable is of type byte.
as well as many of the examples.
AMS doesn't have a byte type (nor does 1364), so what is a single character
of a string variable going to be? I think we might need to add the
byte datatype for this.
-Geoffrey
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by
MailScanner, and is
believed to be clean.
Received on Fri Apr 20 08:05:29 2007
This archive was generated by hypermail 2.1.8
: Fri Apr 20 2007 - 08:05:35 PDT