_kst_

7 ms·

31.
by _kst_ 10mo ago
I see a huge semantic gap between assembly language and C. An assembly language program specifies a sequence of CPU instructions. The mapping between lines of code and generated instructions is one-to-one, or nearly so. A C program specifie
32.
by _kst_ 11mo ago
Are you sure it's been open sourced? I'm reasonably sure you've linked to a site offering pirated copies. There are several links to PDF versions of the book. None of them include either a copyright page or a statement that i
33.
by _kst_ 1y ago
I think you meant to post this comment here: https://news.ycombinator.com/item?id=45481892
34.
by _kst_ 1y ago
OK, but to me a "lockfile" is a file whose existence signals that some resource is locked. https://en.wikipedia.org/wiki/File_locking#Lock_files When I saw the title "We shouldn't have needed lockfi
35.
by _kst_ 1y ago
The author seems to have assumed that readers are going to know that he's talking about NPM and JavaScript, and that "lockfiles" are an NPM-specific feature (to me, it means something completely different). Perhaps that'
36.
by _kst_ 1y ago
I use Ctrl-Space. unbind-key C-b set -g prefix C-Space bind-key C-Space send-prefix I find it a lot easier to type than either Ctrl-A or Ctrl-B.
37.
by _kst_ 1y ago
Not officially, but there are a couple of retronyms. Larry Wall originally wanted to call it "Pearl", but found there was already a language by that name, so he shortened it to "Perl". The name is sometimes expanded as &
38.
by _kst_ 1y ago
Algol 60 also uses the word "call" for parameters as well as functions. It introduced (?) the terms "call by value" and "call by name". For example, in 4.7.5.3: "In addition if the formal parameter is call
39.
by _kst_ 1y ago
"If this standard is accepted, if no magic number you have corrected UTF-8." That's true only if "corrected UTF-8" is accepted and existing UTF-8 becomes obsolete. That can't happen. There's too much exi
40.
by _kst_ 1y ago
"UTF-16 is now obsolete."? That's news to me. I wish it were true, but it's not.
41.
by _kst_ 1y ago
The last US declaration of war was in 1942, against Hungary, Bulgaria, and Romania (allies of Nazi Germany).
42.
by _kst_ 1y ago
C is a relatively low level language, but it is not assembly language. The difference is clear. Assembly language programs specify sequences of CPU instructions. C programs specify runtime behavior.
43.
by _kst_ 1y ago
Sure if the new binary is bitwise identical to the old one, there's no need to release it. But ... "The era of reproducible builds is upon us" What about old code built with old toolchains? And what about organizational pol
44.
by _kst_ 1y ago
My point is that the risk of breaking existing code is the only reason not to apply this change to the standard. My point is also that that's a valid reason to proceed carefully before making the change. Even if the required source cod
45.
by _kst_ 2y ago
A conforming implementation could make string literals modifiable, and (obviously non-portable) code could rely on that. I don't know whether any current compilers do so. I suspect not. Apart from that, it's not about actually m
46.
by _kst_ 2y ago
The C standard, since 1989, has said that attempting to modify the array object corresponding to a string literal has undefined behavior. Whether it "works" or not is not the issue. The problem is that it's currently legal to
47.
by _kst_ 2y ago
Different crew vehicles have different capabilities. Dragon is similar to Soyuz, Apollo, et al. It doesn't have a lot of maneuverability on the way down -- and if it lands in the ocean, it doesn't need it. (Soyuz lands on land; ag
48.
by _kst_ 2y ago
The study is based on 263 galaxies. It should be fairly easy to determine the rotation direction of any (spiral) galaxy we can see, based on reasonable assumptions about the relationship between rotation and the configuration of the spiral
49.
by _kst_ 2y ago
The author is the project editor for the ISO C standard. (And I hardly think that analyzing speculating about the motivation for the author's chosen nickname is constructive.)
50.
by _kst_ 2y ago
Reminds me of the rats we used to have in our garage, that had built nests from our dryer lint. Our dryer lint was largely cat hair.
51.
by _kst_ 2y ago
Mounted on a coconut.
52.
by _kst_ 2y ago
I deal with the main/master brouhaha by using a script I wrote that determines the name of the appropriate branch: #!/bin/bash git remote show origin | sed -n '/^ *HEAD branch: */s//&#x
53.
by _kst_ 2y ago
Apparently both Pelles C for Windows and VAX/VMS use a 32-bit unsigned time_t.
54.
by _kst_ 2y ago
Leap seconds should be replaced by large rockets mounted on the equator. Adjust the planet, not the clock.
55.
by _kst_ 2y ago
Neither C nor POSIX requires time_t to be signed. The Open Group Base Specifications Issue 7, 2018 edition says that "time_t shall be an integer type". Issue 8, 2024 edition says "time_t shall be an integer type with a width
56.
by _kst_ 2y ago
> 1. Don’t assume a terminal type. Look at `TERM` and use termcap/terminfo or a library built atop them for anything beyond line-oriented plain text output, or least assume a plain teletype unless you specifically recognize the user
57.
by _kst_ 2y ago
You can (usually) run your remote tmux in a window in your local tmux session; then you can use the local tmux session's copy/paste features. I commonly run "ssh remote-system" in a tmux window, then attach to a tmux ses
58.
by _kst_ 2y ago
> Don't use color as the only indication of something. The user's terminal might not display it, and it probably won't be preserved in copy&paste into notes. And some of us choose to disable color by default. (Yes, I&#
59.
by _kst_ 2y ago
I got the same thing and worked around it by installing the previous release.
60.
by _kst_ 2y ago
Code that assumes time_t is the same width as int is already broken, and won't work on typical 64-bit systems were int is 32 bits and time_t is 64 bits. In any case, I'm not sure I've ever seen any such code.

More ›