|
|
|
|
|
|
|
Note that the analyze_trades program contains a readily seen
free–malloc pair.
Readily seen free–malloc pairs are indicative of good
programming practice, because you can determine at a glance that memory
allocated by a malloc call is eventually reclaimed by a free.
Thus, you can determine at a glance that the call to malloc does not
cause a memory leak.
The lack of such pairing is considered extremely bad, because it makes memory management much more difficult.