Re: [PATCH master 3/5] Add opcode parameter descriptions

2011-02-04 Thread Iustin Pop
On Fri, Feb 04, 2011 at 05:52:37PM +0100, Michael Hanselmann wrote: > Am 4. Februar 2011 17:51 schrieb Iustin Pop : > > On Fri, Feb 04, 2011 at 05:43:24PM +0100, Michael Hanselmann wrote: > >> These will be used in automatically generated parts of the RAPI > >> documentation. Not all opcodes are do

Re: [PATCH master 3/5] Add opcode parameter descriptions

2011-02-04 Thread Michael Hanselmann
Am 4. Februar 2011 17:51 schrieb Iustin Pop : > On Fri, Feb 04, 2011 at 05:43:24PM +0100, Michael Hanselmann wrote: >> These will be used in automatically generated parts of the RAPI >> documentation. Not all opcodes are documented so far, but each added >> opcode's parameters need to be fully docu

Re: [PATCH master 3/5] Add opcode parameter descriptions

2011-02-04 Thread Iustin Pop
On Fri, Feb 04, 2011 at 05:43:24PM +0100, Michael Hanselmann wrote: > These will be used in automatically generated parts of the RAPI > documentation. Not all opcodes are documented so far, but each added > opcode's parameters need to be fully documented (verified by an > assertion). I wonder if w

[PATCH master 3/5] Add opcode parameter descriptions

2011-02-04 Thread Michael Hanselmann
These will be used in automatically generated parts of the RAPI documentation. Not all opcodes are documented so far, but each added opcode's parameters need to be fully documented (verified by an assertion). --- lib/opcodes.py | 405 +-- test/

Re: [PATCH master 3/5] Add opcode parameter descriptions

2011-02-04 Thread Iustin Pop
On Fri, Feb 04, 2011 at 03:17:10PM +0100, Michael Hanselmann wrote: > Am 4. Februar 2011 14:29 schrieb Iustin Pop : > > On Fri, Feb 04, 2011 at 02:24:16PM +0100, Michael Hanselmann wrote: > >> Am 4. Februar 2011 14:22 schrieb Iustin Pop : > >> > I wonder if it makes sense to keep the parameters doc

Re: [PATCH master 3/5] Add opcode parameter descriptions

2011-02-04 Thread Michael Hanselmann
Am 4. Februar 2011 14:29 schrieb Iustin Pop : > On Fri, Feb 04, 2011 at 02:24:16PM +0100, Michael Hanselmann wrote: >> Am 4. Februar 2011 14:22 schrieb Iustin Pop : >> > I wonder if it makes sense to keep the parameters documented separately, >> > instead of actually embedding the _Doc in opcodes.p

Re: [PATCH master 3/5] Add opcode parameter descriptions

2011-02-04 Thread Iustin Pop
On Fri, Feb 04, 2011 at 02:24:16PM +0100, Michael Hanselmann wrote: > Am 4. Februar 2011 14:22 schrieb Iustin Pop : > > I wonder if it makes sense to keep the parameters documented separately, > > instead of actually embedding the _Doc in opcodes.py. Since these are > > static, I think they wouldn'

Re: [PATCH master 3/5] Add opcode parameter descriptions

2011-02-04 Thread Michael Hanselmann
Am 4. Februar 2011 14:22 schrieb Iustin Pop : > I wonder if it makes sense to keep the parameters documented separately, > instead of actually embedding the _Doc in opcodes.py. Since these are > static, I think they wouldn't actually use per-object memory, and it > would be cleaner. > […] > Thought

Re: [PATCH master 3/5] Add opcode parameter descriptions

2011-02-04 Thread Iustin Pop
On Fri, Feb 04, 2011 at 01:55:11PM +0100, Michael Hanselmann wrote: > These will be used in automatically generated parts of the RAPI > documentation. Not all opcodes are documented so far, but each added > opcode's parameters need to be fully documented (verified by an > assertion). I wonder if i

[PATCH master 3/5] Add opcode parameter descriptions

2011-02-04 Thread Michael Hanselmann
These will be used in automatically generated parts of the RAPI documentation. Not all opcodes are documented so far, but each added opcode's parameters need to be fully documented (verified by an assertion). --- Makefile.am |1 + lib/opdoc.py | 199 ++