-
Notifications
You must be signed in to change notification settings - Fork 6
IP Address Parsers #234
Copy link
Copy link
Open
Labels
🆘 Help WantedExtra attention is neededExtra attention is needed👨🏻🎓 Good First IssueGood for newcomersGood for newcomers🛠 EnhancementNew feature or requestNew feature or request
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
🆘 Help WantedExtra attention is neededExtra attention is needed👨🏻🎓 Good First IssueGood for newcomersGood for newcomers🛠 EnhancementNew feature or requestNew feature or request
Bartosz Adamczewski showed here a "better" way to do IPv4 parsing than the Regex based approach most people use. His approach isn't entirely the best way to do this, and in the comments I made some clarifications. But it did remind me that this should be implemented because of the sheer amount of people who don't know how to efficiently do this.
A very similar approach is possible for IPv6 addresses as well.
The only thing I haven't worked out, because I'm not familiar with .NET's networking components, is with respect to the return type. Is there an IPv4 type? I don't know. Would it make more sense to return a tuple? I don't know.