NSRegularExpression does not match anything after CRLF. Why?
In Swift 4.2, NSRegularExpression does not match anything after CRLF. Why?
let str = "rnfoo"
let regex = try! NSRegularExpression(pattern: "foo")
print(regex.firstMatch(in: str, range: NSRange(location: 0, length: str.count))) // => nil
If you remove "r" or "n", you get a instance of NSTextCheckingResult.
swift
add a comment |
In Swift 4.2, NSRegularExpression does not match anything after CRLF. Why?
let str = "rnfoo"
let regex = try! NSRegularExpression(pattern: "foo")
print(regex.firstMatch(in: str, range: NSRange(location: 0, length: str.count))) // => nil
If you remove "r" or "n", you get a instance of NSTextCheckingResult.
swift
3
It's a range issue. UseNSRange(location: 0, length: str.utf16.count)
instead. If you usedrnfoooooooooooo
(I explicitly add extra char), you would have found it. It's just that your range calculation doesn't cover the "full string range".
– Larme
Nov 21 '18 at 10:25
add a comment |
In Swift 4.2, NSRegularExpression does not match anything after CRLF. Why?
let str = "rnfoo"
let regex = try! NSRegularExpression(pattern: "foo")
print(regex.firstMatch(in: str, range: NSRange(location: 0, length: str.count))) // => nil
If you remove "r" or "n", you get a instance of NSTextCheckingResult.
swift
In Swift 4.2, NSRegularExpression does not match anything after CRLF. Why?
let str = "rnfoo"
let regex = try! NSRegularExpression(pattern: "foo")
print(regex.firstMatch(in: str, range: NSRange(location: 0, length: str.count))) // => nil
If you remove "r" or "n", you get a instance of NSTextCheckingResult.
swift
swift
asked Nov 21 '18 at 10:17
YujiYuji
15019
15019
3
It's a range issue. UseNSRange(location: 0, length: str.utf16.count)
instead. If you usedrnfoooooooooooo
(I explicitly add extra char), you would have found it. It's just that your range calculation doesn't cover the "full string range".
– Larme
Nov 21 '18 at 10:25
add a comment |
3
It's a range issue. UseNSRange(location: 0, length: str.utf16.count)
instead. If you usedrnfoooooooooooo
(I explicitly add extra char), you would have found it. It's just that your range calculation doesn't cover the "full string range".
– Larme
Nov 21 '18 at 10:25
3
3
It's a range issue. Use
NSRange(location: 0, length: str.utf16.count)
instead. If you used rnfoooooooooooo
(I explicitly add extra char), you would have found it. It's just that your range calculation doesn't cover the "full string range".– Larme
Nov 21 '18 at 10:25
It's a range issue. Use
NSRange(location: 0, length: str.utf16.count)
instead. If you used rnfoooooooooooo
(I explicitly add extra char), you would have found it. It's just that your range calculation doesn't cover the "full string range".– Larme
Nov 21 '18 at 10:25
add a comment |
1 Answer
1
active
oldest
votes
In Swift 4 a new initializer of NSRange
was introduced to convert reliably Range<String.Index>
to NSRange
.
Use it always, it solves your issue.
let str = "rnfoo"
let regex = try! NSRegularExpression(pattern: "foo")
print(regex.firstMatch(in: str, range: NSRange(str.startIndex..., in: str)))
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53409827%2fnsregularexpression-does-not-match-anything-after-crlf-why%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In Swift 4 a new initializer of NSRange
was introduced to convert reliably Range<String.Index>
to NSRange
.
Use it always, it solves your issue.
let str = "rnfoo"
let regex = try! NSRegularExpression(pattern: "foo")
print(regex.firstMatch(in: str, range: NSRange(str.startIndex..., in: str)))
add a comment |
In Swift 4 a new initializer of NSRange
was introduced to convert reliably Range<String.Index>
to NSRange
.
Use it always, it solves your issue.
let str = "rnfoo"
let regex = try! NSRegularExpression(pattern: "foo")
print(regex.firstMatch(in: str, range: NSRange(str.startIndex..., in: str)))
add a comment |
In Swift 4 a new initializer of NSRange
was introduced to convert reliably Range<String.Index>
to NSRange
.
Use it always, it solves your issue.
let str = "rnfoo"
let regex = try! NSRegularExpression(pattern: "foo")
print(regex.firstMatch(in: str, range: NSRange(str.startIndex..., in: str)))
In Swift 4 a new initializer of NSRange
was introduced to convert reliably Range<String.Index>
to NSRange
.
Use it always, it solves your issue.
let str = "rnfoo"
let regex = try! NSRegularExpression(pattern: "foo")
print(regex.firstMatch(in: str, range: NSRange(str.startIndex..., in: str)))
answered Nov 21 '18 at 10:44


vadianvadian
148k14159178
148k14159178
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53409827%2fnsregularexpression-does-not-match-anything-after-crlf-why%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
It's a range issue. Use
NSRange(location: 0, length: str.utf16.count)
instead. If you usedrnfoooooooooooo
(I explicitly add extra char), you would have found it. It's just that your range calculation doesn't cover the "full string range".– Larme
Nov 21 '18 at 10:25