On Wed, Oct 19, 2005 at 09:59:15PM +0100, Nicholas Clark wrote: > I think the better solution is going to be to keep them in src/extend.c, > and auto-generate a second file for the vtable calls. So the version attached > generates src/extend_vtable.c
I like that separation. > chromatic: > > I think the correct approach is to annotate vtable.tbl with more > > information -- including the documentation strings -- to make generating > > files easier. > > That seems reasonable. I like the idea of putting the docs together with the declarations. It'll kill the scannability of the file, though. I suppose that's what filters are for. -- Chip Salzenberg <[EMAIL PROTECTED]>
