All of those changes I thought I'd already committed. The taf writer handles

binary data much better, actually escaping it properly and not stopping on null.

Bu::FString has an iterator, it's actually just a raw datatype, but it may have
more function later, so careful assuming that it's a char and using it in any
non-iterator like way.

Also augmented the taf unit test, and added the Bu::CacheCalc base class, the
rest of the simple develpment cycle will happen between here and project hhp.

1 files changed, 25 insertions, 0 deletions

diff --git a/src/fstring.h b/src/fstring.h
index 167c055..91251bc 100644
--- a/src/fstring.h
+++ b/src/fstring.h
@@ -916,6 +916,31 @@ namespace Bu
                         }
                 }
 
+                typedef chr *iterator;
+                typedef const chr *const_iterator;
+
+                iterator begin()
+                {
+                        flatten();
+                        return pFirst->pData;
+                }
+
+                const_iterator begin() const
+                {
+                        flatten();
+                        return pFirst->pData;
+                }
+
+                iterator end()
+                {
+                        return pFirst->pData+pFirst->nLength;
+                }
+
+                const_iterator end() const
+                {
+                        return pFirst->pData+pFirst->nLength;
+                }
+
         private:
                 void flatten() const
                 {