[sv-bc] Merged LRM Draft 2 - comments on strings

From: Bresticker, Shalom <shalom.bresticker_at_.....>
Date: Fri Apr 13 2007 - 08:02:52 PDT
  

Strings are the subject of both 6.14 and 7.6. Although 6.14 is short and
most of the discussion is in 7.6, I don't see the justification for
placing even the short text of 6.14 in a separate section. The two
should be put together. Either in just one section or at most have a
two-sentence paragraph in 6.14 as in done with classes in 6.13. I'm also
not sure whether strings are better discussed in 6 or in 7.

 

String literals are discussed in 5.9 and 11.6.1. Beyond the basic
definition of a string literal, the discussion of what you can do with
them is split up between these two sections roughly evenly, with some
duplication and overlap. Again, either the two sections should be
unified, or 5.9 should be just a minimal definition of string literals,
with all further discussion in 11.6.1.

 

11.6.1 is also a subsection of 11.6, which is Tagged union expressions.
That looks like a mistake. 11.6.1 probably should have been 11.7.

 

Finally, I think the discussions of string literals and string types
should be much closer to each other, since they are so closely related.

 

Some specific comments:

5.9 starts, 'A string literal is a sequence of characters enclosed by
double quotes ("").' The next sentence starts, "A string literal is
enclosed in quotes...". This is duplication.

 

'Nonprinting and other special characters are preceded with a
backslash.': Does this mean that it is allowed to enter a nonprinting
character directly (preceded by a backslash)? What is included in 'other
special characters'? Is the intent of both of these only those
characters in Table 5-1? What about other special characters?

 

 

Following Table 5-1 is "NOTE-the special string characters \v, \f, \a
and \x were added in IEEE 1800-2005.". I don't see any need for this
note.

 

 

That is all I have time for today.

Shalom

Shalom Bresticker

Intel Jerusalem LAD DA

+972 2 589-6852

+972 54 721-1033 

 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



image001.gif
Received on Fri Apr 13 08:03:36 2007

This archive was generated by hypermail 2.1.8 : Fri Apr 13 2007 - 08:04:03 PDT