Hi Rob,
On 2/22/23 23:18, Rob Landley wrote:
16LL on 32 bit systems, but from an "explain what the number is" perspective it
neatly avoids needing to specify a base or units. :)
Right.
What's "fetch"?
A pop culture reference: https://www.youtube.com/watch?v=Pubd-spHN-0
:p
(Part of the
On 2/21/23 19:34, Alex Colomar wrote:
> Hi Rob,
>
> On 2/21/23 18:00, Rob Landley wrote:
>> If you're going to tell people to learn something new: 1<<10 is a kilobyte,
>> 1<<20 is a megabyte, 1<<30 is a gigabyte, and so on. I've sometimes used
>> 16*(1<<30) for clarity.
>
> That's nice, and for
Hi Rob,
On 2/21/23 18:00, Rob Landley wrote:
If you're going to tell people to learn something new: 1<<10 is a kilobyte,
1<<20 is a megabyte, 1<<30 is a gigabyte, and so on. I've sometimes used
16*(1<<30) for clarity.
That's nice, and for code it might be a good idea (although you have to
be
On 2/20/23 09:35, Alex Colomar wrote:
> On 2/20/23 15:29, Stefan Puiu wrote:
>> Hi Alex,
>
> Hi Stefan,
>
>>> 4 KiB is not that much better than 4096, since 4096 is easy to read.
>>> For higher numbers such as 33554432, it becomes more important to use 32
>>> KiB.
>>> For consistency, using 4
On 2/20/23 15:29, Stefan Puiu wrote:
Hi Alex,
Hi Stefan,
4 KiB is not that much better than 4096, since 4096 is easy to read.
For higher numbers such as 33554432, it becomes more important to use 32 KiB.
For consistency, using 4 KiB seems reasonable.
How about using KiB / MiB over a
5 matches
Mail list logo
