[IRCServices] Adding features to services

[Gaven Cohen]

This is just a quickie based on what I read earlier.

If you're going to add features to ircservices, especially if you intend
(or atleast, would like) your features to be incorporated into newer
releases, you MUST make sure ALL your code changes will accomodate ALL
supported IRCds.

The way Andy originally coded services makes this quite easier... you have
a number of compile-time directives which compile in the appropriate code
based on the ircd selected at configuration.

For example:

	#ifdef IRC_DAL4_4_15
		... code ...
	#endif

The expressions available are:

	IRC_DALNET, IRC_DAL4_4_15, IRC_CLASSIC,
	IRC_UNDERNET_NEW, IRC_TS8, IRC_UNDERNET, 

Don't suppose anyone is bored and would like to outline the differences
between these IRCds?  Maybe add it to a programming FAQ for services which
another bored person could make?

Lastly, I agree with the need for an additional list for the CODING of
ircservices.  Feature suggestions and things help requests are fine for a
normal list, but I think a place where people could discuss implementation
of certain things and what they break, how to fix these things, etc, would
be constructive.

- Gav

---
Gaven Cohen aka Kinslayer <dragon at wastelands.net> www.wastelands.net
freelance sysadmin/programmer HABONIM DROR linux, fantasy enthusiast
RSA/1024 0xFC82B78F 4B 43 3C 20 47 58 AF AC  DB 1E 7F 6E 64 08 15 7E

---------------------------------------------------------------
To unsubscribe, send email to majordomo at ender.shadowfire.org
with "unsubscribe ircservices" in the body, without the quotes.