[PATCH 1/3] mime node: Record depth-first part numbers

2012-01-22 Thread Austin Clements
Quoth myself on Jan 18 at 9:12 pm: > Quoth Jani Nikula on Jan 19 at 12:25 am: > > FWIW, I'm not a big fan of casting away const. Either it is const, or it > > isn't. Not very many places would be affected if you dropped the const > > qualifier from the related interface(s) altogether, and things

Re: [PATCH 1/3] mime node: Record depth-first part numbers

2012-01-22 Thread Austin Clements
Quoth myself on Jan 18 at 9:12 pm: Quoth Jani Nikula on Jan 19 at 12:25 am: FWIW, I'm not a big fan of casting away const. Either it is const, or it isn't. Not very many places would be affected if you dropped the const qualifier from the related interface(s) altogether, and things would

[PATCH 1/3] mime node: Record depth-first part numbers

2012-01-19 Thread Jani Nikula
On Wed, 18 Jan 2012 15:28:25 -0500, Austin Clements wrote: > This makes the part numbers readily accessible to formatters. > Hierarchical part numbering would be a more natural and efficient fit > for MIME and may be the way to go in the future, but depth-first > numbering maintains compatibility

[PATCH 1/3] mime node: Record depth-first part numbers

2012-01-18 Thread Austin Clements
Quoth Jani Nikula on Jan 19 at 12:25 am: > On Wed, 18 Jan 2012 15:28:25 -0500, Austin Clements > wrote: > > This makes the part numbers readily accessible to formatters. > > Hierarchical part numbering would be a more natural and efficient fit > > for MIME and may be the way to go in the future,

[PATCH 1/3] mime node: Record depth-first part numbers

2012-01-18 Thread Austin Clements
This makes the part numbers readily accessible to formatters. Hierarchical part numbering would be a more natural and efficient fit for MIME and may be the way to go in the future, but depth-first numbering maintains compatibility with what we currently do. --- mime-node.c | 33

[PATCH 1/3] mime node: Record depth-first part numbers

2012-01-18 Thread Austin Clements
This makes the part numbers readily accessible to formatters. Hierarchical part numbering would be a more natural and efficient fit for MIME and may be the way to go in the future, but depth-first numbering maintains compatibility with what we currently do. --- mime-node.c | 33

Re: [PATCH 1/3] mime node: Record depth-first part numbers

2012-01-18 Thread Jani Nikula
On Wed, 18 Jan 2012 15:28:25 -0500, Austin Clements amdra...@mit.edu wrote: This makes the part numbers readily accessible to formatters. Hierarchical part numbering would be a more natural and efficient fit for MIME and may be the way to go in the future, but depth-first numbering maintains

Re: [PATCH 1/3] mime node: Record depth-first part numbers

2012-01-18 Thread Austin Clements
Quoth Jani Nikula on Jan 19 at 12:25 am: On Wed, 18 Jan 2012 15:28:25 -0500, Austin Clements amdra...@mit.edu wrote: This makes the part numbers readily accessible to formatters. Hierarchical part numbering would be a more natural and efficient fit for MIME and may be the way to go in the