--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [IRCServices Coding] svcs5 - request
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20svcs5%20-%20request&In-Reply-To=023d01c196d9%24811dad80%240300a8c0%40asi200">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000089.html">
+ <LINK REL="Next" HREF="000091.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[IRCServices Coding] svcs5 - request</H1>
+ <B>Finny Merrill</B>
+ <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20svcs5%20-%20request&In-Reply-To=023d01c196d9%24811dad80%240300a8c0%40asi200"
+ TITLE="[IRCServices Coding] svcs5 - request">griever at t2n.org
+ </A><BR>
+ <I>Sun Jan 6 13:05:14 PST 2002</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000089.html">[IRCServices Coding] svcs5 - request
+</A></li>
+ <LI>Next message: <A HREF="000091.html">[IRCServices Coding] svcs5 - request
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#90">[ date ]</a>
+ <a href="thread.html#90">[ thread ]</a>
+ <a href="subject.html#90">[ subject ]</a>
+ <a href="author.html#90">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Sun, 6 Jan 2002, Ben Goldstein wrote:
+
+Well the thing is, you would need a pointer to a function
+that prints it to a file, as we dont know whether it contains
+ints, chars, shorts, longs, or whatever.
+
+><i> This is an excellent idea. I don't think it would be that big of a deal to
+</I>><i> add this to a final database version in 5.0-release, depending on how far
+</I>><i> off that is.. Keep up the good work, guys.
+</I>><i>
+</I>><i> -- Ben Goldstein (<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">beng at nc.rr.com</A>)
+</I>><i>
+</I>><i> ----- Original Message -----
+</I>><i> From: <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">v13 at priest.com</A>>
+</I>><i> To: <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net</A>>
+</I>><i> Sent: Sunday, January 06, 2002 8:52 AM
+</I>><i> Subject: [IRCServices Coding] svcs5 - request
+</I>><i>
+</I>><i>
+</I>><i> If you realy want other people to write useful modules, then it should be
+</I>><i> possible for each module to extend the NickServ and ChanServ (and even the
+</I>><i> others) databases. I suppose that having a:
+</I>><i>
+</I>><i> struct ext_list {
+</I>><i> struct ext_list *prev, *next;
+</I>><i> long id;
+</I>><i> size_t size;
+</I>><i> void *buf;
+</I>><i> };
+</I>><i>
+</I>><i> that will form a list for each nickname/channel whould be what we need. It
+</I>><i> should be easy to save it using the existing database format.
+</I>><i> Also by providing some functions like:
+</I>><i>
+</I>><i> struct ext_list *get_extlist_memb(struct ext_list *head, long id);
+</I>><i>
+</I>><i> void update_extlist_memb(struct ext_list **head, long id, size_t size,
+</I>><i> void *buf);
+</I>><i>
+</I>><i>
+</I>><i>
+</I>><i>
+</I>><i>
+</I>><i> ------------------------------------------------------------------
+</I>><i> To unsubscribe or change your subscription options, visit:
+</I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A>
+</I>><i>
+</I>
+
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000089.html">[IRCServices Coding] svcs5 - request
+</A></li>
+ <LI>Next message: <A HREF="000091.html">[IRCServices Coding] svcs5 - request
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#90">[ date ]</a>
+ <a href="thread.html#90">[ thread ]</a>
+ <a href="subject.html#90">[ subject ]</a>
+ <a href="author.html#90">[ author ]</a>
+ </LI>
+ </UL>
+
+</body></html>