libznc #133

Open
opened 2026-10-05 04:00:42 +02:00 by adam · 1 comment
Owner

For start, just to be usable from C++.
After that from python, maybe perl.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

For start, just to be usable from C++. After that from python, maybe perl. ## <bountysource-plugin> Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/653-libznc?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin> <!-- github-sync-id:6006976 -->
Author
Owner

I saw this report and wondered "WTF?!". Then I read my IRC backlog. So let's some important information here:

Having a libznc could make it easier to write tests for specific parts.

However, I don't think we would want to make "the real ZNC" work with libznc, too. That just asks for people to make it load the wrong libznc because they have that other znc instance laying around, too.

I saw this report and wondered "WTF?!". Then I read my IRC backlog. So let's some important information here: Having a libznc could make it easier to write tests for specific parts. However, I don't think we would want to make "the real ZNC" work with libznc, too. That just asks for people to make it load the wrong libznc because they have that other znc instance laying around, too. <!-- github-comment-id:7480097 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#133