Title
Default constructed match_results behavior for certain operations
Status
resolved
Section
[re.results.acc]
Submitter
BSI

Created on 2010-08-25.00:00:00 last changed 170 months ago

Messages

Date: 2011-05-21.21:15:19

Proposed resolution:

Addressed by paper n3158.

Date: 2010-10-24.00:00:00

[ 2010-10-24 Daniel adds: ]

Accepting n3158 would solve this issue.

Date: 2010-10-31.20:26:19

[ Resolution proposed by ballot comment: ]

Add to match_results::operator[], match_results::prefix and match_results::suffix:
Requires: !empty()

Date: 2010-10-24.03:04:13

Addresses GB-126

It's unclear how match_results should behave if it has been default-constructed. The sub_match objects returned by operator[], prefix and suffix cannot point to the end of the sequence that was searched if no search was done. The iterators held by unmatched sub_match objects might be singular.

History
Date User Action Args
2010-11-18 12:46:23adminsetstatus: nad editorial -> resolved
2010-11-11 01:27:21adminsetstatus: open -> nad editorial
2010-10-31 20:26:19adminsetmessages: + msg5212
2010-10-25 00:09:15adminsetmessages: + msg5098
2010-10-24 03:04:13adminsetmessages: + msg4944
2010-08-25 00:00:00admincreate