summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarko Živković <[email protected]>2014-06-12 23:43:59 +0000
committerMarko Živković <[email protected]>2014-06-12 23:43:59 +0000
commita576088a6e9567fbffd13ce23a32a460a785832d (patch)
tree591bb5f12a48d9704dceb1443eb4ba8d1ddefa63
parent9f789867f5593acc29461f51871d06327746752b (diff)
Corrected info text
git-svn-id: https://svn.code.sf.net/p/xlogo4schools/svn/trunk@4 3b0d7934-f7ef-4143-9606-b51f2e2281fd
-rw-r--r--logo/src/xlogo/gpl/x4s_info.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/logo/src/xlogo/gpl/x4s_info.html b/logo/src/xlogo/gpl/x4s_info.html
index ff7458e..699fd50 100644
--- a/logo/src/xlogo/gpl/x4s_info.html
+++ b/logo/src/xlogo/gpl/x4s_info.html
@@ -37,6 +37,6 @@
<li>
The Graphics are much smoother due to another rendering configuration.</li>
<li>
- Measured on a Sierpinski Triangle of depth 9, XLogo4Schools is around 25% faster than XLogo (16s vs. 21s on my machine). It is even faster, when many procedures are added to the workspace. XLogo uses a stack to manage its procedures and it uses O(N) string comparisons to find a procedure. Interestingly, the hash operations push and pop are not really used. XLogo4Schools uses a HashMap that usually works in O(1).</li>
+ Measured on a Sierpinski Triangle of depth 9, XLogo4Schools is around 25% faster than XLogo (16s vs. 21s on my machine). It is even faster, when many procedures are added to the workspace. XLogo used a stack to manage its procedures which took O(N) string comparisons to find a procedure. Interestingly, the designated stack operations push and pop are not really used. For the same purpose, XLogo4Schools uses now a HashMap that usually works in O(1).</li>
</ul></body>
</html> \ No newline at end of file