_kst_

24 ms·

211.
by _kst_ 5y ago
My first thought was to wonder why I'd want a README in a shared object.
212.
by _kst_ 5y ago
Any such warning needs to be clear to the employee . There's no particular requirement for it to be clear to the rest of us.
213.
by _kst_ 5y ago
On Unix-like systems, you can't use '\0' in a path name. I think that's also the case on Windows. Nor can you use '/', so trying to use that as a file extension would be almost equally silly.
214.
by _kst_ 5y ago
How about a language named "."? The source code for the "hello, world" program would be in a file called "hello..". Or Ctrl-G (BEL). Just doing a directory listing would make your terminal beep. Or LF if you re
215.
by _kst_ 5y ago
> or is an operator in C++ Yes. > and if you #include <iso646.h> in C Sort of. As a preprocessor token, it's an identifier that happens to be the name of a macro. As a token (after preprocessing), it becomes the "||&qu
216.
by _kst_ 5y ago
I read the rules incorrectly. It appears that "0xfor" is a valid way to represent the two tokens "0xf" and "or". The rule, which I initially misinterpreted, is: > Whitespace is needed between two tokens on
217.
by _kst_ 5y ago
You're right, and I was wrong. I dislike the rule, and I strongly think that "0xfor" should require whitespace between "0xf" and "or" (I'm sure that influenced my reading), but you're right abo
218.
by _kst_ 5y ago
"1+2" is a valid expression consisting of the three tokens "1", "+", and "2". It's permitted to omit whitespace between those tokens. The question is whether "0xfor" is a valid way to r
219.
by _kst_ 5y ago
The cited documentation says: > Whitespace is needed between two tokens only if their concatenation could otherwise be interpreted as a different token (e.g., ab is one token, but a b is two tokens). The two tokens in this case are &quot
220.
by _kst_ 5y ago
I should have stated that more clearly. In Python, "or" is both an operator and a keyword. In most languages, numeric literals, identifiers, and keywords cannot be adjacent, but any of then can be adjacent to a token that consists
221.
by _kst_ 5y ago
1+2 is a valid expression consisting of 3 tokens, "1", "+", and "2". In most languages, numeric literals, identifiers, and keywords cannot be adjacent, but any of them can be adjacent to an operator. The odd th
222.
by _kst_ 6y ago
It's mildly annoying that the web site is encoded in Latin-1 but displayed in UTF-8. The xml content says 'encoding="ISO-8859-1"', but the server says 'Content-Type: text/html; charset=utf-8'. It caus
223.
by _kst_ 6y ago
Fortunately, ESR specifically says it's a backronym. > “Scram” was in origin a backronym for “Safety Cut Rope Axe Man” coined by Enrico Fermi himself.
224.
by _kst_ 6y ago
I'm curious why my question is getting downvotes.
225.
by _kst_ 6y ago
Thanks for replying. It doesn't sound like I'm your target audience. Best of luck.
226.
by _kst_ 6y ago
I haven't taken a look at it yet. Can you summarize what it offers that Donovan & Kernighan's "The Go Programming Language" doesn't? (Sincere question, not being snarky.)
227.
by _kst_ 6y ago
Well, you can certainly think of "long" and "short" as adjectives, but the grammar doesn't treat them that way. "long", "short", "signed", "unsigned", "int", "f
228.
by _kst_ 6y ago
> It makes sense long would have needed a comment. I think you misunderstood. There's no explanatory comment. The "long" keyword is commented out , meaning that it was planned but not yet implemented. ...
229.
by _kst_ 6y ago
strncpy() is not a "safer" strcpy(). It can avoid some errors involving writing past the end of the target array ( if you tell it the correct length for that array), but it's not a true string function, and it can leave the
230.
by _kst_ 6y ago
There's a bigger potential problem with the *scanf() functions than performance. They are inherently unsafe for reading numeric input. For example, if you do something like this: int n; sscanf("9999999999999999999999999&
231.
by _kst_ 6y ago
UPDATE: The README.md has now been updated with a link to the older version that describes what the project is about. Thanks to the maintainer for doing this. The remainder of this comment is obsolete (except for the last paragraph). As oth
232.
by _kst_ 6y ago
Sure, but not nearly enough for practical energy storage and retrieval.
233.
by _kst_ 6y ago
It would be great if (a) you could safely prevent it from releasing its energy when you don't want it to ( KABOOM! ), and (b) you could efficiently capture and use the energy it releases, which is going to consist largely of gamma rays
234.
by _kst_ 6y ago
I get interesting results if I draw a figure 8 (or a figure ∞). I wonder if it's treating one of the lobes as having negative density.
235.
by _kst_ 6y ago
Google had the most complete archive of comp.lang.c (and the rest of Usenet). That archive is now inaccessible. Users posting to comp.lang.c through Google Groups were a problem -- especially with the recent bug that caused GG posts to co
236.
by _kst_ 6y ago
The numbers, as in "bash(1)" refer to sections of the manual. "Info" is a different documentation format, most commonly used for GNU tools (including bash). The section numbers don't generally apply to info document
237.
by _kst_ 6y ago
Years ago, I wrote a filter that reversed lines and reversed characters within each line after padding with blanks. I ran a text file through it, printed the result, turned the paper upside down, and complained to a sysadmin that the printe
238.
by _kst_ 6y ago
UTF-640K?
239.
by _kst_ 6y ago
At an SF convention party, someone said, "To be or not to be". I replied "equals FF".
240.
by _kst_ 6y ago
A mathematician, a physicist, an engineer, and a computer scientists are all asked to test the hypothesis that all odd numbers greater than 2 are prime. (Apologies in advance to engineers.) The mathematician: 3 is prime, 5 is prime, 7 is pr

More ›