summary refs log tree commit diff stats
path: root/web/question.txt
diff options
context:
space:
mode:
authorAndreas Rumpf <andreas@andreas-laptop>2010-03-20 20:13:14 +0100
committerAndreas Rumpf <andreas@andreas-laptop>2010-03-20 20:13:14 +0100
commite62a02d5af90e243bf5d84fdf2ac3567e94bdf58 (patch)
tree62e2cf9b1760ba01df94c1b01f7260321021ee1f /web/question.txt
parent7d6de1cf90858700733091b9a592b2fac7549af5 (diff)
downloadNim-e62a02d5af90e243bf5d84fdf2ac3567e94bdf58.tar.gz
versioning for GTK wrappers
Diffstat (limited to 'web/question.txt')
-rwxr-xr-xweb/question.txt5
1 files changed, 2 insertions, 3 deletions
diff --git a/web/question.txt b/web/question.txt
index 6cd44391d..bce9c0c74 100755
--- a/web/question.txt
+++ b/web/question.txt
@@ -53,10 +53,9 @@ and their interactions are subject to change.
 How fast is Nimrod?
 -------------------
 Benchmarks have not been ported yet and support for threads is missing. But in
-the worst case, you can get exactly the same performance as in C if you decide 
+the worst case, you can get the same performance as in C if you decide 
 to write as low-level Nimrod code as C requires you to do. That said the only
-overhead Nimrod has over C is the GC which has been tuned for years (and is 
-significantly faster than the Boehm GC).
+overhead Nimrod has over C is the GC which has been tuned for years.
 
 
 Compilation