Re: [Boost-bugs] [Boost C++ Libraries] #3703: Request for ability to specify description column width

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #3703: Request for ability to specify description column width
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-12-03 10:42:38

#3703: Request for ability to specify description column width
-------------------------------+--------------------------------------------
  Reporter:  Chard             |       Owner:  s_ochsenknecht               
      Type:  Feature Requests  |      Status:  closed                       
 Milestone:  Boost 1.42.0      |   Component:  program_options              
   Version:  Boost 1.41.0      |    Severity:  Cosmetic                     
Resolution:  fixed             |    Keywords:  description column formatting
-------------------------------+--------------------------------------------

Comment(by s_ochsenknecht):

 Replying to [comment:9 Chard <boost@…>]:
 > Hi Sascha
 >
 > I've had a bit more of a look at the changes, and there's a couple of
 points to note:
 >
 > 1. I had called the original description length variable:
 {{{min_description_length}}}, this has been renamed to
 {{{description_length}}}.  The "{{{min_}}}" part does add some semantic
 meaning to the usage because the length that is specified is not an
 absolute.

 Yes, you're right. I agree that {{{min_description_length}}} might be the
 better name here. I wasn't 100% aware that the description could be
 longer. I'll change that.


 > 2. By tying the default argument for the description length to
 {{{(default_line_length / 2)}}} it does mean that existing code that
 specifies the {{{line_length}}} argument will still compile, but with a
 potentially different display.  The minimum description width will still
 be 40, regardless of the specified {{{line_length}}}.  However, I suspect
 this is a minor point because for most cases the output should look
 ''better''.

 Yes, I wouldn't change it now since it can not be detected within the
 constructor if the default parameter was used or not. Or we end up with 1
 or more constructor overloads, which I would like to avoid. Most likely
 the user will specify all parameters or none, I guess.


 Thanks & regards,
 Sascha

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/3703#comment:10>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.