Tox, the distributed instant messaging program, just got a new GUI client that is written in PURE C WITHOUT ANY DIRTY TOOLKITS. Calls Xlib and the win32 api directly.
>>43 You dickshit, this i) makes use of non standard functions (vasprintf) that is SLOWER than snprintf and even more slower than sprintf and you don't even make use of its output ii) INT_FAST8_MAX is not a type and you need to #include <stdint.h> first
But notsecure only uses ~0 only when assigning values to unsigned stuff. So there's no portability issue.
Concerning the int.h or a test macro to handle weird systems, I think he has other priorities, such as getting video working. Would you mind doing a pull request or posting the necessary changes in this thread? That would be pretty helpful.
Name:
Anonymous2014-06-23 17:19
so many autists antibumping
Name:
Anonymous2014-06-23 17:22
typedef uint8_t char_t;
WTHHH this is lame as hell, it uses uint8_t in a place where it is not needed (breaking comportability) and it violotates the POSIX standard (you can not define things that end with _t)
I don't really think the developer has time for this stuff right now, he is working of getting video, now that audio was added last week. Pull requests would surely make him happy, I believe. If you aren't in the mood, just keep complaining and I hope he eventually deal with all by himself.
>>57 I will be eagerly waiting. For some reason, it makes me happy seeing developers working together. It gets me almost moist. Something that I would love is it to compile without warnings, but there are so many of them, that I doubt it will ever be done.
Trivia: even most uTox's icons are written in C. svg is bloat. Eventually, it will all be C. Even notification sounds will be in C, probably some sine waves or something (can't remember the developer exact words).
>>71 Stop astroturfing, it's obvious you're the OP of this thread. You're risking a ban. We've had a few threads about Tox already, most of us just aren't interested in /g/ projects.
>>72 Sorry, I didn't know we had threads about it earlier, never saw one. Anyway, I am mostly talking about uTox, a Tox client. Not Tox itself. Sorry, Mr. Anonymous.
The tox developers are horrible people. They are ignorant and feel they are `competing' with the other open source telephony/chat alternatives. They are also making their users vulnerable by encouraging them to use a p2p software in pre alpha stage. The only software I will write for tox will be maleware. now please go away before I turn your wall paper in goatse.