torproject / tor Public
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove util and compat #193
Remove util and compat #193
Conversation
These had become wrappers around their fd and socket variants; there were only a few users of the original functions still remaining.
(Term is short for terminal)
I'm not sure of the best place to put this header long-term, since both or/*.c and tools/tor-resolve.c use it.
This is now just a collection of frequently-used headers.
.gitignore
Outdated
| @@ -195,6 +195,8 @@ uptime-*.json | |||
| /src/lib/libtor-meminfo-testing.a | |||
| /src/lib/libtor-net.a | |||
| /src/lib/libtor-net-testing.a | |||
| /src/lib/libtor-osinfo.a | |||
| /src/lib/libtor-osinfo-testing.a | |||
So here is an idea. How about we have an "os" library for which we could put all the things we use to interact with the operating system.
I'm thinking about this get_uname() but also, set file desc, get available memory, etc... ?
Hm. I'm not so sure there. Isn't everything that ends in a syscall "something that interacts with the operating system?"
| @@ -54,6 +54,7 @@ COMMONHEADERS = \ | |||
| src/common/compat_libevent.h \ | |||
| src/common/handles.h \ | |||
| src/common/procmon.h \ | |||
| src/common/socks5_status.h \ | |||
To respond to the commit message, my guts feeling tells me that we probably want a socks5 library at some point for which it should be (I think!) only visible to the "tor client" component.
No description provided.
The text was updated successfully, but these errors were encountered: