Note that there are some explanatory texts on larger screens.

plurals
  1. USJasper
    primarykey
    data
    text
    plurals
    1. CO@Oskar Kjelling should be, could be, might be. A minimal code sample is usually a very small application (or website in this case) that shows the problem, which can make it a lot easier to fix and makes sure that we have enough information to fix the problem. So, yeah, it might not be necessary, but I would request it, as it would give us a better point to start from.
      singulars
    2. COLet me esplain a little more. First I create my Monster and put them in my "array" (I am not sure yet which container I will use) and then I start handing out Monster* to member variables (let's say `myMonsterCollection` and `yourMonsterCollection`) some of those pointers might get copied (to `MonsterDisplayers`) and they might move from my collection to your collection and vice versa (in actuality there are more than two locations). I run a loop over the "array" to see which monsters want to register events. The original "array" is then really only kept as the "owner". Is this a good design?
      singulars
    3. COBasically, there is the initialization of the data and then there's no more insertions or deletions, until destruction. However, as the only way I will be accessing the data is in a loop from n=0 to n=size, I didn't think that the performance would be all that different... Actually, as far as I know, unless you are using "at" (or an overloaded operator with the same effect) there is not much of a disadvantage to lists, is there?
      singulars
 

Querying!

 
Guidance

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