fprawn

8 ms·

1.
by fprawn 12y ago
If you have time, can you expound on this? Is there, perhaps, an open source project that handles NULL returns from malloc in this way you could point me to?
2.
by fprawn 12y ago
I'll clarify this. I'm not saying you shouldn't ever check return values, that's obviously not the right thing to do. And of course there are exceptions to the general rule. If you're allocating a large chunk of mem
3.
by fprawn 12y ago
Memory allocation failures are virtually non-existent in modern desktop computers. Good practice is to not test return values from malloc, new, etc. Memory can be allocated beyond RAM size, so by the time a failure occurs your program reall
4.
by fprawn 13y ago
SEEKING WORK - San Francisco Bay Area or Remote 10+ years C/C++ video game development, scientific visualization, and real time image processing. Polyglot programmer that works mainly in C/C++, Python, Perl, and PHP on Android&#x2
5.
by fprawn 13y ago
This is amazing. He's come up with completely new ways to do graphics on modern CPUs. This is genuinely impressive stuff and the breadth of it is mind blowing. It's upsetting how dismissive of his work he can be, he deserves to be
6.
by fprawn 13y ago
There's a lesson here about how sometimes it's okay to fit your data to your code. This was, afterall, in php for years without causing much, if any, problems for end users. I guess there won't be much agreement here on HN, b
7.
by fprawn 13y ago
This is true only if the source image is smaller than the destination image. In the article, the source image is shown as the same size as the destination, and includes a large white border that can be clipped without the inner image being
8.
by fprawn 13y ago
This is really neat, but seems to neglect an alternative (and just as simple) method. Instead of traversing through each pixel of the source buffer, traverse through each pixel of the destination buffer sampling the correct pixels from the