nviennot

19 ms·

61.
by nviennot 14y ago
6. Computers. a value that a program or operating system assumes, or a course of action that a program or operating system will take, when the user or programmer specifies no overriding value or action.
62.
by nviennot 15y ago
I had to read it 5 times to understand the meaning... From what I understand: the more dyno you have, the less each dyno can do. Which is funny when you think about it, becuause your Heroku bill increases linearly with the number of dyno.
63.
by nviennot 15y ago
It's an early version of it, but support iOS (arm), and MacOS (x86_x64, no i368). I'd be happy to hear your comments :) Nico.
64.
ShowHN: An objective-c method call tracer(github.com)
1 points by nviennot 15y ago|1 comments
65.
by nviennot 15y ago
Same here, I guess we are done. Not my fault ;)
66.
by nviennot 15y ago
There is something pretty cool that one can do with the FTP protocol: FXP transfers to perform an inter-server file transfer: https://en.wikipedia.org/wiki/File_eXchange_Protocol
67.
by nviennot 15y ago
You are right, and there are other issues: - I don't return the proper return value (should not return the number of bytes from the color strings) - I don't handle the case where writev() returns a number of bytes between 0 and count (e.g.
68.
by nviennot 15y ago
Indeed: https://github.com/sickill/stderred/pull/1
69.
by nviennot 15y ago
Ho... now it makes sense.. http://techcrunch.com/2011/05/12/swallowing-puke/
70.
by nviennot 15y ago
gem should be free.. I hate this idea. What if I want to fork the code ? And I don't want to put licenses all around the place when it comes to deployments.
71.
by nviennot 15y ago
I lost my previous account password that I haven't used in a very long time...
72.
by nviennot 15y ago
1) freeing memory automatically for you. That's under the table :) 2) Absolutely 3) No. it's just that memory management related issues are really nasty. On the other hand, adding a new printf() function won't do much harm.
73.
by nviennot 15y ago
Hum.. the Linux Kernel, it's pretty big :) You get kmalloc() and kfree(), which are very similar to malloc() and free(). (Okey you also get kmem_cache_alloc()/kmem_cache_free() which gives you the ability to provide a ctor/dtor, but they ar
74.
by nviennot 15y ago
Writing a pair of constructor/destructor is not a problem. tmalloc() adds a layer of complexity that is unhealthy to C programs. Are the few seconds you save by using tmalloc() really worth the hours spent to debug memory leaks 6 months lat