Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1
  • Thanks Will and Neil for your help. The problem was proposed (or imposed) as a safe development approach. The idea is that if we use static memory and if something is wrong, the program will crash at the first run or/and will not pass the test phase. Having a static matrix in a class having the class itself defined as static are not good options. The solution of having a class managing all used memory seems to be the best approach, I just hope that don't get into troubles later and end up having to change my code. KISS approach, yes this is a Memory Pool problem. Commented Jul 29, 2013 at 16:52