summaryrefslogtreecommitdiffstats
authorJimmy Tang <jtang@tchpc.tcd.ie>2011-07-23 09:46:45 (GMT)
committer Jimmy Tang <jtang@tchpc.tcd.ie>2011-07-23 09:46:45 (GMT)
commit3667e4123bdb86002316498b16285f10ec831c45 (patch) (side-by-side diff)
treed53e938b0df428cd01a5625945523b524c403d81
parent5f24fdb159051ce679665cff6b79e1e2602610c5 (diff)
downloadwiki-3667e4123bdb86002316498b16285f10ec831c45.tar.gz
wiki-3667e4123bdb86002316498b16285f10ec831c45.tar.bz2
wiki-3667e4123bdb86002316498b16285f10ec831c45.tar
typos
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--blog/posts/Memory_debuggers_and_garbage_collectors_for_C__47__C++.mdwn14
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
--- 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
@@ -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.
[google-perftools]: http://code.google.com/p/google-perftools/
[gc]: http://www.hpl.hp.com/personal/Hans_Boehm/gc/