Str-to-IP strange results for some IP numbers

[deceased]

As a programmer I often confuse Christmas and Halloween,

Spoiler

25DEC == 31OCT

0xDEAD

[rolfk]

---

@altenbach wrote:

IMHO, LabVIEW should drop the octal interpretation (or also support the hexadecimal interpretation). Seems half-baked. 😉

---

While LabVIEW does a tiny bit extra work here, the real meat of the entire implementation for String to IP and IP to String is located in the Winsock driver. If you want this option removed you have to adres this to Microsoft and request a change in the Winsock driver. Guess how much chance that makes! 

Besides that is standard functionality of the Berkeley Socket library (from which the Winsock library was derived) and absolutely NOBODY is going to remove that from there!

[altenbach]

---

@rolfk wrote:

---

---

While LabVIEW does a tiny bit extra work here, the real meat of the entire implementation for String to IP and IP to String is located in the Winsock driver.

---

Yes, I wasn't sure how much is external to LabVIEW. Nothing needs to be done.

TRUE STORY: I remember running into this problem probably almost 20 years ago when I had the brilliant (not!) idea to format IP addresses with leading zeroes (%03d for each octet) so the tables look nicer in a fixed-width font, just to have it blow up in my face when trying to read them again later. 😄