Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fexl
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
31.
▲
Fexl now using purely functional evaluation
(github.com)
1 points
by
fexl
12y ago
|
0 comments
32.
▲
New Fexl Release (default is eager evaluation instead of lazy)
(github.com)
1 points
by
fexl
12y ago
|
0 comments
33.
▲
by
fexl
13y ago
Same here -- I played it in 1974 on an HP 2000F minicomputer via a teletype located in a converted janitor's closet at my high school. The author mentions the lack of ability to renumber the lines in a BASIC program, but I'm quite
34.
▲
by
fexl
13y ago
I see a funny thing when I test it against yahoo.com: $ ./Heartbleed yahoo.com:443 (bunch of returned bytes) 2014/04/08 12:59:46 yahoo.com:443 - VULNERABLE Near the front of the returned bytes is the sequence "
35.
▲
by
fexl
13y ago
No it's a good point actually, and it pays to know your context. Frankly, looking at the 118 lines in assert.h, it does considerably more than I really need. Instead of this: assert(buf->pos < buf->str->len); I coul
36.
▲
by
fexl
13y ago
Right now, in my code, assert(0==1) produces this output to stderr: run: run.c:422: main: Assertion `0==1' failed. Aborted That is what I want. You are correct. If I build with -DNDEBUG=1, then the assert is completely ignore
37.
▲
by
fexl
13y ago
Assertion failure messages are sent to stderr. Production code can capture that as it wishes.
38.
▲
by
fexl
13y ago
I love C but I use it in a disciplined way. Here's the email I sent to the author: James: I liked your article on range checking. I'm very keen on assertions, for example here: https://github.com/chkoreff/Fex
39.
▲
by
fexl
13y ago
I've been doing the 135-degree thing for many years, much like the picture there, but without the foot rest. I make sure to squirm around on occasion, and I get up and stretch and walk with the dog regularly. So far so good.
40.
▲
Range-Checks and Recklessness
(prog21.dadgum.com)
22 points
by
fexl
13y ago
|
19 comments
41.
▲
by
fexl
13y ago
"You can't discriminate based on race - that limits choice but who would support the contrary?" If someone refuses to serve or otherwise interact with me on account of my race, I would not use the threat of deadly force to ch
42.
▲
by
fexl
13y ago
I couldn't take the new Cosmos. It's heavy on special effects and light on content, which is delivered in a breathless style that makes me feel like I'm on a third grade field trip. The old Cosmos, with Carl Sagan, was fasci
43.
▲
by
fexl
13y ago
When I visited Sweden I spoke with a friend there who had been born and raised way up in the north of Sweden. He said the people there would bury and ferment all sorts of things, including seal meat, whale blubber, and birds sewn into seal
44.
▲
by
fexl
13y ago
Good question. I go with -O3 because it does even more optimizations, but to be quite candid I really don't know what impact -fpredictive-commoning, -ftree-vectorize, and others have on my resulting machine code, if any. I did a quick
45.
▲
by
fexl
13y ago
Agreed, see my post above about -std=c99.
46.
▲
by
fexl
13y ago
I tend to go with: gcc -c -Wall -Werror -std=c99 -pedantic -O3 I use -std=c99 because I use these two features of C: 1. Mixed declarations and code, e.g. double x = 4.8 * 5.3; printf("x = %.15g\n", x); double y = 8.
47.
▲
by
fexl
13y ago
It's possible. I'm wary of anything from Google.
48.
▲
by
fexl
13y ago
Yeah, though I refactored their code to avoid the "goto", as an exercise. It would indeed facilitate making separate functions for common swaths of code, notably the duplicate code blocks beginning with ReadyHash and ending with
49.
▲
by
fexl
13y ago
A few days ago I wrote up something on this same issue: http://fexl.com/goto-considered-harmful However, after discussing the issue on the cryptography mailing list, I realized that the really serious problem here was not t
50.
▲
Installing FreeBSD 10 to ZFS with a script
(blather.michaelwlucas.com)
2 points
by
fexl
13y ago
|
1 comments
51.
▲
by
fexl
13y ago
Looks like yet another dependency that I'll have to build from source code, and test, fix, and refactor myself.
52.
▲
Hey Apple! GOTO Considered Harmful.
(fexl.com)
1 points
by
fexl
13y ago
|
0 comments
53.
▲
by
fexl
13y ago
Good point. Particularly interesting because you are suggesting an inverse correlation between work hours and wealth. Can you point me to some evidence for that? I might expect some sort of parabola, e.g. people who work very few hours te
54.
▲
China's Worst Self-Inflicted Environmental Disaster
(io9.com)
5 points
by
fexl
13y ago
|
0 comments
55.
▲
by
fexl
13y ago
He wants to ban the use of a public ledger with private and public keys.
56.
▲
by
fexl
13y ago
Yeah, should be "leery", as in "The clear ends of FRNs for either transacting in illegal goods and services or speculative gambling make me leery of its use."
57.
▲
by
fexl
13y ago
I bet if he had redirected the output to /dev/null it wouldn't be slower with 'B'.
58.
▲
by
fexl
13y ago
And no BASE jumping either.
59.
▲
by
fexl
13y ago
I've taken to defining "@" as the Y combinator, so it looks kind of like a "goto" label for looping, e.g.: (@\fact\n \n==n <= n 0 1 (* n (fact (- n 1)))) (The \n==n forces an eager evaluation, to avoid bui
60.
▲
by
fexl
13y ago
I did see that comment. However, I was addressing Mr. Watt's conclusion from the story: "What this means then is that money is nothing but bookkeeping." I disagree. What that story means is that the people were left holdin
More ›