Talk:3102: Reading a Big Number

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

Is the final character a 6, or is it a theta? 2A02:F6E:A36E:0:F0F1:E624:A18C:EDC2 14:05, 13 June 2025 (UTC)

The across line is curvy, so most likely a "6". 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). 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. 90.73.80.27 15:41, 13 June 2025 (UTC)

I don't care how it is stored in source code, either decimal, hex, binary, etc., upper or lower is fine. The output on screen, if hex, should always be in upper case. If grouped, hex is in groups of 4 and never commas. SDSpivey (talk) 12:58, 15 June 2025 (UTC)

r/unexpectedfactorial Randall Monroe, shame on you! 50.195.132.249 (talk) 14:58, 13 June 2025 (UTC) (please sign your comments with ~~~~)

Surely this is just one line of a CSV file... 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 2806:106e:19:81f2:fc2c:11d2:79fa:615c (talk) 16:31, 13 June 2025 (UTC) (please sign your comments with ~~~~)

Also an unusual and possibly broken CSV. 000 values are uncommon (they are usually just 0), and the " (or '') 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. 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. 74.202.210.170 19:19, 13 June 2025 (UTC)

Remember, kids: always end your strings with a NUL 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. ;) 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. 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). 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. -- Angel (talk) 21:26, 13 June 2025 (UTC)

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

If you turn #c2ef46 into a color https://www.perbang.dk/rgb/c2ef46/, it's a brilliant lime green. Dogman15 (talk) 10:05, 14 June 2025 (UTC)

If you add the decimal representation of the RGB color, you get 503 - awfully close to 504.Lopped (talk) 14:38, 15 June 2025 (UTC)

Does that mean this is a brat number? 82.13.184.33 15:57, 16 June 2025 (UTC)

The RGB is meaningless in this case as it's #00c2ef46 meaning that it's fully transparent. 2001:1C02:1A9D:9700:51CF:BA7C:200D:2C3F 17:52, 16 June 2025 (UTC)

Wait, why does the table jump straight from billions to quadrillions? Where's trillions? Is this an error or one of those UK-vs-US-billion situations? 185.231.139.156 18:34, 14 June 2025 (UTC)

Oh! It's because the comic doesn't comment on the 'trillions' comma. I get it now. It's 'cause I'm dumb. 185.231.139.156 18:37, 14 June 2025 (UTC)

LOL, nice recovery! Ianrbibtitlht (talk) 16:05, 15 June 2025 (UTC)

I always start at the right and work to the left. So then when I actually start reciting what the number is, I know if it's quintillions – or whatever – that I'm dealing with. Yorkshire Pudding (talk) 11:01, 15 June 2025 (UTC)

People always read numbers RTL. Just check yourself. 185.7.43.114 (talk) 14:25, 16 June 2025 (UTC) (please sign your comments with ~~~~)

Seems to me that the table format is appropriate, given the three kinds of info (number group, comic's comment, explanation). But I don't think it makes sense to have the table sortable. BunsenH (talk) 17:04, 16 June 2025 (UTC)

That's interesting, the sorting is the only reason I could come up with for using a table instead of a list. A table is much less accessible than a list, doesn't work on phones, is harder to maintain, and I don't think it's needed here. I just converted a random table in the latest comic that was just NUMBER - RANDALL'S TEXT - EXPLANATION. I just don't see why this wiki is in love with tables. --FaviFake (talk) 20:53, 16 June 2025 (UTC)