Channels ▼

Open Source

Pure C++ Options Classes

A Manual Setters Overloading Solution

One cure is to manually overload all the inherited setters in the derived options class, changing the return types to "follow" the class, that is, with covariant return types:

struct CheckBox: AbstractButton
   struct Params: AbstractButton::Params
      bool isAutoValue;
      Params(): isAutoValue( true ) {}
      int hTextAlign() const
     { return AbstractButton::Params::hTextAlign(); }
     Params& hTextAlign( int v )
          return static_cast<Params&>(
              AbstractButton::Params::hTextAlign( v )
  bool isAuto() const { return isAutoValue; }
  Params& isAuto( bool v ) { isAutoValue = v; return *this; }
explicit CheckBox( Params const& = Params() )
          : AbstractButton( params )

The reason that also the hTextAlign getter, not only the setter, is overloaded here, is that any hTextAlign overload hides or "shadows" the base class implementations. This hiding rule is so perplexing to C++ novices that it has its own FAQ entry, but without it the setter overloading couldn't work since one can't overload solely on return type (which brings in a terminology issue: is "overload" the right word?).

Why Manual Setters Overloading Can Be Impractical

Manually implemented setters work, but the source code size overhead of introducing a single new option in a derived class can be quite large when the base class has many options. And when a new option is introduced in a base class, or an option is renamed or removed, then all the derived classes' options classes have to be manually updated. If a base class has n options, and has a chain of d derivations down to some class, each of which introduces 1 new option, then the number of setter implementations for that chain is (d+1)·m + (d2+d)/2. If every class in that chain of n = d+1 classes defines m options, then the number of setter implementations is m·(n2+n)/2. And even though we're talking very small numbers here this means that the manual setters overloading approach can often be wholly impractical.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.