Netch

6 ms·

1.
by Netch 4mo ago
From a bystanderʼs POV it is excessively hard to memorize all the mess with multiple different extensions. The naming style doesnʼt alleviate the task. But this is a typical issue in the whole RISC-V ecosystem. What Iʼm slightly confused fo
2.
by Netch 4mo ago
A normal situation in my tasks is when the working copy contains lots of changes that are used for debug (mainly prints) but these changes shall not be committed to the proposed change. For this, even interactive adding (`git add -i`) does
3.
by Netch 1y ago
Slightly side note - I donʼt understand why C++ invents new stdio based functions like std::print but rejects to import funopen() or fopencookie() which make stdio flexible similar to iostreams. As for me it should have been done ≈20 years
4.
by Netch 2y ago
With the manner exposed by the most feature-full DEs, Iʼd expect setting default to ~/Cache (not ~/cache, the latter is for the userʼs discretion). But, I tend to agree with the main articleʼs premise that without a special teachi
5.
by Netch 2y ago
Nice work! Perseverance to find the root cause in such an unfriendly environment as any bootstrap is what saves all us from the civilization crash...
6.
by Netch 2y ago
RISC-V designers explicitly declare in their base specification: "The AMOs were designed to implement the C11 and C++11 memory models efficiently." So at least one example is present.
7.
by Netch 2y ago
> Python might have used array[~0] instead This is what was once added to C#: arr[^idx], when this ^idx is mapped to a special object, typically optimized then out. arr[^0] means the last element.
8.
by Netch 2y ago
> In Europe, we typically mark the ground-floor as floor-zero, _Western_ Europe. Eastern Europe prefers 1-based numbering. The reason, typically assumed, is that thermal isolation, required due to colder winters, causes at least one stai
9.
by Netch 2y ago
> find the convention used in many countries of numbering building floors starting with zero to be more logical. Ukrainian here. Multi-floor buildings always have at least one stair section to first floor due to need of thermal basement
10.
by Netch 2y ago
This division, using SRT loop with 2 bit output per iteration, perhaps would have already been microcoded - but using the lookup table as an accelerator. An alternative could use a simpler approach (e.g. 1-bit-iteration "non-restoring&
11.
by Netch 2y ago
Filename character set and its interpretation shall be controlled per directory or, at least, per FS. This pertains not only to permitted set like with or without LF, but to collation rules as well (including case insensitivity with cases l
12.
by Netch 2y ago
OK let them add an explicit check to standard tools, and/or to open(), mkdir(), etc. with O_PORTABLECHARS. And an environment option to disable this check. Why they force the restriction at syscall level?
13.
by Netch 2y ago
> it seems that glibc does not support it `iconv` does, and this is enough in common. Among with tons of eerie EBCDIC/whatever...
14.
by Netch 2y ago
> That can only be a bug - UTF-32/UCS-4 never saw external use I regularly use `iconv -t utf-32be | hd` to look what a bizarre sequence is denoting yet another weird symbol like an itchy hedgehog. And what is a real reason to disall
15.
by Netch 2y ago
But at least a programmer shall be aware to call it (whatever API is used).
16.
by Netch 2y ago
> You're not limited to 650MB provided you use UDF rather than ISO 9660. You donʼt take into account case of booting real ISO on an old hardware. If it doesnʼt know DVD, chance of UDF support in BIOS is vague. More so, itʼs possible
17.
by Netch 2y ago
> Makes you wonder why this isn't part of the C++ standard library itself. Plainly no need if there is a separate easily attachable library (and with permissible license). What C++ had to do - provide character (char{8,16,32}_t) and
18.
by Netch 2y ago
> There’s no excuse. Until mid-2000s there was no certainty Unicode will eventually defeat competitors. In real it havenʼt fully yet - GB2312 and Tron are still locally prevailing, and IBM still jogs with EBCDIC. But at its early times n
19.
by Netch 2y ago
> In C# I can simply do this: "hello world".ToUpper(); Hmm still actual: https://www.moserware.com/2008/02/does-your-code-pass-turkey...
20.
by Netch 2y ago
All the code which is not in hot path may conform to any rules, and typically is designed according to something like SOLID, to make understanding and maintenance as simple as possible (and suitable to any average coder). All the code which
21.
by Netch 2y ago
Really I would have concur with the author if dealing again and again with a need to fit the media contents into 650MB (if it is intended to be put at real ISO) or to guarantee how combination of 1) realmode bootloader + 2) UEFI bootloade
22.
by Netch 2y ago
Live CD is mainly replaced with live USB, even if it is called the same nickname.
23.
by Netch 2y ago
> QEMU running Windows for x86 on an M1 isn't very fast either. It seems the main obstacle is in paging where x86 4KB clashes with Apple 16KB (ARM/64 supports multiple sizes), so, 2-level paging canʼt aid and an emulator has to
24.
by Netch 2y ago
> You're saying you can't think of one context where a trade of between largest supported int value vs total bytes of the message is a reasonable one? Seems you have pretty misread me. Well, "any system" (where system
25.
by Netch 2y ago
Most cases an initial estimate of change cost is utterly overstated because emotional and reluctant to change. (And, well, this fact is also abused by wreckers who explain any reasonable objection with this factor;))
26.
by Netch 2y ago
All this suggests the insane Windows time (64 bits of 100ns periods since 01.01.1601 00:00 GMT as it would have been Gregorian) sometimes has it small advantages - both an excellent discretion and will work even the whole galaxy will be con
27.
by Netch 2y ago
FreeBSD was also more radical in dealing with off_t which became 64 bits since 2.0. Linux still has rudiments of old size in its 32-bit versions. > One of which was the automatic cast of 32 bit function arguments to 64 bit during the fun
28.
by Netch 2y ago
> Code that assumes time_t is the same width as int is already broken You missed the point. It is meant that code _built for the same target_ "assumes" all instances use the same definition of time_t, and not about such a guara
29.
by Netch 2y ago
> SCTP > It also has multiplexing built right in. It is not. You canʼt stop, for example, receiving from stream 0 during getting high-priority data from stream 9. No userlevel API allows to specify "now receive a message exactly
30.
by Netch 2y ago
> If you really want real numbers passing them as decimal string is actually sensible. Hexadecimal, if so. Nearly any decent modern language and runtime can it. $ python >>> import math >>> math.pi.hex()

More ›