4 ms·
You just added two entries to the maximum number of digits a processor can handle at once. I didn't get your suggested solution in full: how would you hande the
by sgy 13y ago
You just added two entries to the maximum number of digits a processor can handle at once.
I didn't get your suggested solution in full: how would you hande the extra identifier?
- frou_dh 13y agoThey only become digits if and when they're parsed out of the textual query string as such. The structure of HTTP query strings is not something the processor cares or even knows about. To it, "=1,333" isn't an equals sign followed by two comma-separated numbers, it's simply 6 bytes of data. The meaning of that data is an application level concept.
- sgy 13y agoWhat I meant with digits is zeros and ones, of course not strings/characters. There's no disagreement about the data context in the lower level. To be more clear, let's suppose that the maximum a CPU can read at once is one character (8 bits). If we went by your suggestion to add one or two extra characters [on the high level], or 16 bits [on the lower level], the processor won't be able to handle the 24 (8 + 16) at one time, simply because the max is 8 at a time.
- frou_dh 13y agoThis moves firmly into the absurd given a computer is an imperative machine with memory that's persistent between steps.
- Edman274 13y agoAre you asking "how can a computer compare strings that are longer than their native word size"
- sgy 13y agoWell, not exactly, but rather the most efficient way to deal with elements (big numbers, in specific) that aren't going to fit in a single CPU register. Current libraries I've had a look at has some limitation on the speed of calculations.