goirc

Author	SHA1	Message	Date
Alex Bramley	557b178798	NFI where i was up to, store state.	2011-07-17 13:14:25 +01:00
Alex Bramley	762ba1e599	Type inference proves too costly for ragel-based config... On the one hand, the complex ragel solution is explicit about the config syntax and requires little heavy lifting on the Go side, but the ragel definition is overly complex, too rigid and produces bloody huge binary output. On the other the simple ragel solution can provide pretty much the same syntax with some type conversion, but the reflection magic to pack this into objects correctly is done much better by the JSON module. Forcing parsing of everything tostrings results in lots of nasty if/case statements in the Go code. JSON has another benefit in that the config serialisation is two-way, allowing for web or IRC based configuration. It's a pity it's a bugger to edit by hand.	2011-02-22 21:26:48 +00:00
Alex Bramley	f99a2c6bb8	Make sure we're using SVN ragel; add default Link constructor.	2010-12-01 23:07:49 +00:00
Alex Bramley	7e90299992	Add parser.go so people don't have to build SVN ragel ;)	2010-11-28 18:09:33 +00:00
Alex Bramley	1566d7772c	Add oper parsing, standardise ragel naming, change config.	2010-11-28 18:08:11 +00:00
Alex Bramley	22ccce6bb2	Ragel based config file parser, ftw.	2010-11-28 16:48:02 +00:00
Alex Bramley	377fbcd3af	WIP on config parser before attempting to learn FSMs	2010-11-27 14:12:12 +00:00
Alex Bramley	b2539c0063	Initial commit of vague hackery for a go IRCd.	2010-11-21 20:07:31 +00:00