Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My 77 uses were macros that did atomically check a flag.

My point was that that does not scale.

Also, I didn't have a scheduler. The point of interrupts is that you don't need a scheduler.



>My point was that that does not scale.

Thanks for the clarification.

>Also, I didn't have a scheduler. The point of interrupts is that you don't need a scheduler.

I think where we digress in position is that I do not think you have a good justification for the statement "be scared of signals" because, after all, you are clearly not scared of them and have decided to bend them to your own thoughts on how best to optimize your application, so its sort of ingenuous to hold the position having completely wiped "the standard way to do high-performance signal-handling" from your slate, to put your own special case forward by example. You're clearly not scared of them.

I'm calling you out on it because signals are absolutely not scary, but maybe talking about them with other experts can be.

Your case is more an example of how unscary signals are - but you've opted for longjmp()'s (which are, imho as a systems programmer, a far more cromulant fear) in your code as a solution to a problem which I don't think is really typical.

Thus, not really scary at all.

Well, it was a fun read of some code, and thanks for bc anyway.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: