Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parsing char8_t, char16_t, char32_t and wchar_t #4

Closed
VladimirShaleev opened this issue Apr 14, 2024 · 0 comments · Fixed by #5
Closed

Parsing char8_t, char16_t, char32_t and wchar_t #4

VladimirShaleev opened this issue Apr 14, 2024 · 0 comments · Fixed by #5
Assignees
Labels
enhancement New feature or request

Comments

@VladimirShaleev
Copy link
Owner

Parsing incoming Unicode strings

For example, if we have an incoming line with an incorrect character in the ip addresses, for example:

ipv4_address::parse(u8"127.\ud55c.\U00010348.1")

In the exception we should receive the following message:

try {
    ipv4_address::parse(u8"127.\ud55c.\U00010348.1");
} catch (const std::exception& exc) {
    std::cout << exc.what() << std::endl;
    // unexpected unicode symbol {U+D55C} in address 127.{U+D55C}.{U+10348}.1
}
@VladimirShaleev VladimirShaleev added the enhancement New feature or request label Apr 14, 2024
@VladimirShaleev VladimirShaleev self-assigned this Apr 14, 2024
@VladimirShaleev VladimirShaleev linked a pull request Apr 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant