Detect loops in /Pages structure

Pushing inherited objects to pages and getting all pages were both
prone to stack overflow infinite loops if there were loops in the
Pages dictionary. There is a general weakness in the code in that any
part of the code that traverses the Pages structure would be prone to
this and would have to implement its own loop detection. A more robust
fix may provide some general method for handling the Pages structure,
but it's probably not worth doing.

Note: addition of *Internal2 private functions was done rather than
changing signatures of existing methods to avoid breaking
compatibility.

1 files changed, 3 insertions, 0 deletions

diff --git a/TODO b/TODO
index 777d7038..41d2c625 100644
--- a/TODO
+++ b/TODO
@@ -1,6 +1,9 @@
 5.2.0
 =====
 
+ * Before release: remember to bump minor shared library version since
+   new methods were added (even though private).
+
  * Figure out what about a3576a73593987b26cd3eff346f8f7c11f713cbd
    broke binary compatibility.