In our previous episode, ik said: > There are sometimes way to "see" that you have memory leak in a code without > using any sort of profiler. > For example using new/getmem on a local variable without releasing it etc... > > Does FPC know how to find this places on compile time and at least issue a > warning about it ?
Is this a suitable task for a compiler? Maybe it is a task better suited to an external profiler. _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
