Reputation
2,214
Top tag
Next privilege 2,500 Rep.
Create tag synonyms
Badges
9 22
Newest
 Nice Answer
Impact
~205k people reached

Apr
10
awarded  Nice Answer
Apr
1
awarded  Yearling
Feb
29
comment How should we represent an IPv6 address with port number in text?
For instance, it turns out that this is acceptable, for an IPv6 mapped IPv6: ::ffff:10.1.2.3:1234, without the square brackets. (Though that is not valid in URL use, it is not ambiguous.)
Feb
29
comment How should we represent an IPv6 address with port number in text?
In fact RFC 5952 has a more well-rounded answer in section 6. The [ADDR]:PORT isn't the only notation; just the one that should be used in URLs according to RFC 3986.
Feb
29
awarded  Scholar
Feb
29
accepted How should we represent an IPv6 address with port number in text?
Feb
29
comment How should we represent an IPv6 address with port number in text?
You forgot to copy over the RFC reference from the SO answer. :)
Feb
29
comment How should we represent an IPv6 address with port number in text?
It's not a duplicate of any question here; those are off topic on those sites. The question isn't about a broken piece of code, so it's not appropriate for StackOverflow, and it's not a sysadmin issue for ServerFault. It's a "conceptual questions about software development": what do I put into the tostring method of an IPv6 socket address class.
Feb
29
asked How should we represent an IPv6 address with port number in text?
Dec
23
awarded  Good Answer
Dec
16
answered Why does the Lisp community prefer to accumulate all the parentheses at the end of the function?
Dec
16
comment Marriage of Lisp and LaTeX - has it been done?
By the way, LaTeX pays homage to Lisp by calling alternative versions of operators that do something slightly different with a * suffix. Lisp has let and let* and so on, LaTeX has \section and \section*.
Nov
25
revised Benefit of non-volatile access to volatile objects being undefined?
Remove stray text at bottom.
Sep
24
comment Benefit of non-volatile access to volatile objects being undefined?
What volatile does is quite clear. Objects which are volatile have to have values (at sequence points) which agree with the abstract semantics. Also, a footnote says that in an implementation in which objects, at sequence points, have the values which agree with the abstract semantics (i.e. a not very well optimized implementation), then volatile is redundant.
Sep
24
comment Benefit of non-volatile access to volatile objects being undefined?
Those aren't implementation-specific behaviors. The volatile uses with setjmp and signal handlers are required by ISO C. volatile defeats the optimizations which could cause a restored setjmp context to restore stale register-cached values of locals. It also defeats the optimizations that could cause accesses to a global sig_atomic_t variable to ignore updates by a signal handler.
Sep
24
comment Benefit of non-volatile access to volatile objects being undefined?
Programs which use memory-mapped hardware invoke undefined-behavior pretty much no matter how they gain access to it. I'm only interested in the portable C uses. volatile is required for C declared objects in two cases: objects that are modified since state is recorded with setjmp, but before the state is restored with longjmp, whose values are then used upon restoration. Secondly, asynchronous signal handlers may only modify volatile sig_atomic_t objects. I'm only interested in the portable C semantics.
Sep
24
awarded  Student
Sep
24
asked Benefit of non-volatile access to volatile objects being undefined?
Jun
23
revised In C++ why and how are virtual functions slower?
Mention shared libs.
May
21
comment Short circuit evaluation, is it bad practice?
No, the language isn't clever. The && operator is designed to work that way and must not evaluate the right hand side if the left is false. "Short circuiting" isn't an optimization; it is semantics. If it isn't done, programs break. Just like programs would break if if statements suddenly started evaluating else clauses even when the conditions are true.