Joseph Wright wrote:
>>  * The overall structure of the code starts with lots of little things
>> (macros concerned with parsing specific argspecs) and ends (I'm
>> guessing, from xparse-alt) with putting them together. The more literate
>> approach would be to start with the big picture -- either from the "what
>> goes on at run-time" or "what goes on at define-time" point of view --
>> so that one knows what the little things will fit into when one gets to
>> them.
> 
> This reflects how I think, I suspect. I like to start at the low level
> and work up, hence variables come first (after the lead-off), then
> internal functions, the user functions. I've divided internal functions
> into what seem to me to be logical "blocks", then I do everything
> alphabetically. So I can quickly find a function if I know its name. (I
> never read code from start to end, or even in typeset form. I always
> read it in my editor, find a function, read it, then find the next
> function, etc. So for me alphabetical is best.) In my defence, xparse
> was in roughly the same order before any changes were made by me.

I should add that I'm happy to alter things: obviously, I might need
some suggestions on an order more helpful to other people.
-- 
Joseph Wright