|author||Jimmy Tang <firstname.lastname@example.org>||2011-07-23 09:46:45 (GMT)|
|committer||Jimmy Tang <email@example.com>||2011-07-23 09:46:45 (GMT)|
|commit||3667e4123bdb86002316498b16285f10ec831c45 (patch) (side-by-side diff)|
1 files changed, 7 insertions, 7 deletions
diff --git a/blog/posts/Memory_debuggers_and_garbage_collectors_for_C__47__C++.mdwn b/blog/posts/Memory_debuggers_and_garbage_collectors_for_C__47__C++.mdwn
index 06e4561..65e28e7 100644
@@ -21,13 +21,13 @@ around to using it, I'm quite happy to say that it's pretty easy to
use and it seems okay for doing garbage collection. It is particularly
useful but requires a small bit of work with existing codes.
-I was however surprised with [google-perftools], I had realised that
-it was a malloc() replacement and that it provided a bunch of
-profiling and checking features. Best of it is relatively easy to use,
-short and concise. I've yet to read up on the garbage collection
-features in this library, assuming there is garbage collection. I can
-see myself using this library a bit more when I write C or when I have
-to fix someone elses code.
+I was however surprised with [google-perftools], I had never
+realised that it was a malloc() replacement and that it provided a
+bunch of profiling and checking features. Best of all it is relatively
+easy to use, short and concise. I've yet to read up on the garbage
+collection features in this library, assuming there is garbage
+collection. I can see myself using this library a bit more when I
+write C or when I have to fix someone elses code.