Talk:3102: Reading a Big Number

2025-06-14T08:38:28Z

2A02:2455:1960:4000:74EC:297D:7E70:AAB0:

avrayter [[User:Avrayter|Avrayter]] ([[User talk:Avrayter|talk]]) 12:27, 13 June 2025 (UTC) how do you add links

Is the final character a 6, or is it a theta? [[Special:Contributions/2A02:F6E:A36E:0:F0F1:E624:A18C:EDC2|2A02:F6E:A36E:0:F0F1:E624:A18C:EDC2]] 14:05, 13 June 2025 (UTC)
: The across line is curvy, so most likely a "6". [[User:SDSpivey|SDSpivey]] ([[User talk:SDSpivey|talk]]) 14:14, 13 June 2025 (UTC)

I would have to fire any programmer that output hex in lowercase (or put commas in triplets for hex). [[User:SDSpivey|SDSpivey]] ([[User talk:SDSpivey|talk]]) 14:14, 13 June 2025 (UTC)
: You may be firing about half of the programmers then :) I don't think there is a rule here, both forms are common, but I guess that there are holy wars to fight. [[Special:Contributions/90.73.80.27|90.73.80.27]] 15:41, 13 June 2025 (UTC)

r/unexpectedfactorial Randall Monroe, shame on you!

Surely this is just one line of a CSV file... [[Special:Contributions/86.144.197.52|86.144.197.52]] 15:51, 13 June 2025 (UTC)
: That is actually a strong justification!! I'd like to see the headers, tho xD
: Also an unusual and possibly broken CSV. 000 values are uncommon (they are usually just 0), and the " (or <nowiki>''</nowiki>) may be used for quoting. There is no way to tell how it will parse as CSV is not a well defined format. There is a standard, RFC 4180, but it is not always followed. [[Special:Contributions/90.73.80.27|90.73.80.27]] 18:03, 13 June 2025 (UTC)
: could be CSFWV = comma-separated-and-fixed-width-values where the values are also 0-padded so that it works in both their CSV parsers and their fixed-width parsers for compatibility. [[Special:Contributions/74.202.210.170|74.202.210.170]] 19:19, 13 June 2025 (UTC)

Remember, kids: always end your strings with a NUL [[Special:Contributions/93.36.184.28|93.36.184.28]] 15:56, 13 June 2025 (UTC)

By my reckoning, if you set a 78RPM record playing, and waited for it to have spun the amount of arcseconds specified (by that point in the "number", you'd be waiting a tad over 7 ''billion'' times the current age of the universe. I might have erred by a magnifude or three (forgot if I divided number of days down to get number of years, etc, and I much prefer to work with Long Scale billions, so maybe I did it slightly wrong when working with the inferior kind), but... Well, it doesn't really matter ''quite'' so much, I suspect. ;) [[Special:Contributions/82.132.246.216|82.132.246.216]] 17:11, 13 June 2025 (UTC)

I remember, years ago, seeing calculators using single quotes as thousands-separators. But never a double-quote. Interestingly, the C++ standard (as of the 2014 release) permits single-quote characters as an arbitrary digit separator for numeric literals. They are ignored by the compiler, but can be useful for making code more readable (e.g. every 3 decimal digits or every 4 hex digits). See also https://en.cppreference.com/w/cpp/language/integer_literal.html. [[User:Shamino|Shamino]] ([[User talk:Shamino|talk]]) 19:02, 13 June 2025 (UTC)

Apart from the quotation mark, this still matches [my hex number regex](https://stackoverflow.com/a/76696505/6743127). [[User:Fabian42|Fabian42]] ([[User talk:Fabian42|talk]]) 19:22, 13 June 2025 (UTC)

Oooh, looks like an IPv9 address, but they're using ',' instead of '🕴️' to separate triplets for some reason. The clusters with an extra leading 0 indicate that they're in octal instead of base64. -- [[User:Angel|Angel]] ([[User talk:Angel|talk]]) 21:26, 13 June 2025 (UTC)

Randall, how in tarnations did you find out my password? 08:38, 14 June 2025 (UTC)

explain xkcd - User contributions [en]

Talk:3102: Reading a Big Number