Databases
StackOverflow2013
Postsdbo
POParametized class creation with assert of parameter presence. Use factory?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POParametized class creation with assert of parameter presence. Use factory?
    primarykey
    data
    text
    <p>I spend about 2 hours reading a lot of factory related topics and I still am not sure if this would be the right approach.</p> <p>Here is the thing: I have an <strong>Enemy</strong> class that has contains member variables like <em>name</em>_ and <em>health</em>_. I want to create instances of it with different values of these member variables and my first approach was to get the parameters from a static array with the properties:</p> <pre><code>Enemy::Enemy(int type) : name_(properties[type].name), health_(properties[type].health) { ... } </code></pre> <p>The problem here is that I can't check if the array <em>properties</em> is already filled. I would have to check it from outside by calling a static <em>Enemy::initArray()</em> function but this would defeat the encapsulation of the <strong>Enemy</strong> class.</p> <p>Is this the time to create a factory that would initialize the <em>properties</em> array in it's constructor? And then create Enemies with:</p> <pre><code>Enemy* EnemyFactory::create(type); </code></pre> <p>I read that usually factories are created when you have complex class hierarchies or the factory caller only needs to know the interface of the created classes. I only need the encapsulation of the array creation and verification. Is there a "lighter" solution?</p> <p><strong>EDIT:</strong> I'll try to be more clear:</p> <p>1.) I think I know <strong>how</strong> to create a factory. The main question is whether there is an <strong>alternative</strong>!</p> <p>2.) I don't want to set the properties inside the object but use initialization lists. If I do the former I can just check the array in the constuctor and don't need the factory at all.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USproblemofficer
    1. USproblemofficer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POParametized class creation with assert of parameter presence. Use factory?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POParametized class creation with assert of parameter presence. Use factory?
      1. USproblemofficer
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload