thedigitalengel

13 ms·

61.
by thedigitalengel 15y ago
We should have something like GWT that compiles .NET to whatever Microsoft thinks developers should use.
62.
by thedigitalengel 15y ago
Writing a decent C++ compiler is /really/ hard, but why bother about a solved problem! http://news.ycombinator.com/item?id=2549657
63.
by thedigitalengel 15y ago
That was an uninformed ad-hominem from my side. My bad, I apologize.
64.
by thedigitalengel 15y ago
What I meant was that unless you're writing a C++ compiler, these reasons should not longer bother you. Even if you are, you're free to leverage off clang's lexer and parser. Otherwise it is a lot like saying Java is bad because it is hard
65.
by thedigitalengel 15y ago
Firstly, half of the time the guy bitches about flaws with the compiler, and not the languages (Page 0 to 6). Most of the bitching is about language features which exist. If you don't like auto_ptr then DON'T use auto_ptr! C++ at least allo
66.
by thedigitalengel 15y ago
Can you be more specific? I have a counter example (assuming I've understood you): /* C / int foo () { FILE x = fopen("bar"); return 0; } /* C++ */ int foo () { ifstream in("bar"); return 0; }
67.
by thedigitalengel 15y ago
To put that in perspective, 128 bytes is an x64 program's stack's red zone. :D
68.
by thedigitalengel 15y ago
Most projects have a set of coding guidelines. I don't see why it cannot specify things like: "Don't use operator overloading!". Google does, for one thing. Without discipline both C and C++ will blow you up completely. With some discipline
69.
by thedigitalengel 15y ago
C and C++ have considerably overlap in use cases, which is what makes this argument valid. Comparing C or C++ to Ruby or LISP is stupid.
70.
by thedigitalengel 15y ago
You don't get a warning because the program is doing exactly what you asked it to do. You said a C with x = 0 is equal to 'true'. And you said a D with f = 0.0 is equal to 'true'. By transitivity of equality ...
71.
by thedigitalengel 15y ago
Most of the points mentioned in that particular link pertains why both C and C++ are inferior to languages like LISP and Python which have garbage collectors, weak type system and the like. The bitching about bad compile time errors has b
72.
Facebook Development Tools(github.com)
1 points by thedigitalengel 15y ago|0 comments
73.
On Monads, Part II(playingwithpointers.com)
2 points by thedigitalengel 16y ago|0 comments
74.
On Monads(playingwithpointers.com)
5 points by thedigitalengel 16y ago|0 comments
75.
by thedigitalengel 16y ago
This is obviously not a universal formula, but I started out with "Practical Common LISP"; and then went on to SICP, translating the Scheme code into CL code as I went along. I then followed this by "On LISP". For someone who does not know
76.
Mithridatism(en.wikipedia.org)
2 points by thedigitalengel 16y ago|0 comments
77.
by thedigitalengel 16y ago
Please mention if you're interested in hiring a remote intern.
78.
Scientists store 900,000GB of data in 1 gram of E. coli bacteria(thinkdigit.com)
2 points by thedigitalengel 16y ago|0 comments
79.
by thedigitalengel 16y ago
x86 is cache-coherent; we can directly modify code at runtime and expect things to work.
80.
by thedigitalengel 16y ago
Please mention if you're willing to hire a remote intern.
81.
by thedigitalengel 16y ago
You may want to show them how you can generate code by emitting assembly hex-codes into a block of memory and then _call_ the block of code after casting it into a function pointer.
82.
(Relatively) Painless Command Line Parsing With C(playingwithpointers.com)
2 points by thedigitalengel 16y ago|0 comments
83.
Painless Command Line Argument Parsing in C(github.com)
10 points by thedigitalengel 16y ago|5 comments
84.
by thedigitalengel 16y ago
http://github.com/sanjoy/L A call-by-name untyped lambda calculus evaluator. I have no clue what to do with it.
85.
Uses for a Lambda Calculus Reduction Machine.
3 points by thedigitalengel 16y ago|0 comments
86.
by thedigitalengel 16y ago
That imposes an uncalled for runtime overhead. A better way would be to implement it using code-patching, by overwriting the instructions at specific pre-determined locations which will then cause the thread to halt when executed.
87.
by thedigitalengel 16y ago
Even with the threads possibly stopping at unsafe points, a mostly precise scan (saving the last stack frame) can be done if the stack maps are maintained for all the call-sites.
88.
by thedigitalengel 16y ago
What happens if the native code enters, say, an infinite loop?
89.
The Management Myth
3 points by thedigitalengel 16y ago|2 comments
90.
by thedigitalengel 16y ago
The early to bed and early to rise paradigm works incredibly well for me - there is something about being up before sunrise that boosts my productivity. I sleep 5 hours when I'm not working out and around 8 hours when I am; which means my s

More ›