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

What I'm suggesting is entirely compatible with tame. It doesn't change anything about the implementation, but prevents you from accidentally calling functions that would error out.

The only thing that my suggestion optionally changes is that using, eg, socket() would be a compile time error AND a runtime error, instead of only a runtime error, if you tell the system that you want it. Don't define the macros to disable functions that you are trying to make uncallable? Your code is 100% unaffected.



It's not the same because the restrictions aren't in effect at the start of the program until the tame call is made.


Again, this doesn't change anything on that front. You just don't define the declaration hiding macros in the files that do the init.

It just prevents random-seeming issues off of the common path due to calling a function that you shouldn't have called.




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

Search: