This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of NAD status.

1452. "target sequence" is not defined

Section: 32.9.5 [re.results.acc] Status: NAD Submitter: BSI Opened: 2010-08-25 Last modified: 2016-01-28

Priority: Not Prioritized

View all other issues in [re.results.acc].

View all issues with NAD status.


Addresses GB-125

The term "target sequence" is not defined (32.9.5 [re.results.acc] p. 2).

[ Resolution proposed by ballot comment: ]

Replace "target sequence" with "string being searched/matched"

[ 2010-11-01 Daniel comments: ]

The proposed resolution looks incomplete to me, there are more normative usages of the term target sequence in clause 28, e.g. 32.11.2 [re.tokiter] p. 7.

[2011-03-22 Madrid meeting: Moved to NAD]


Standard is correct as written

Proposed resolution:

Wording changes are against N3126. They are intended not to conflict with the wording changes suggested by n3158.

Change 32.9.5 [re.results.acc] p. 2 as indicated:

difference_type position(size_type sub = 0) const;

2 Returns: The distance from the start of the target sequencestring being matched to (*this)[sub].first.