The new taf interfaces seem to work just fine, except for saving and that loaded

TafNode structures are immutable, it all looks really good.  Saving should be a
snap, and the immutable part I'm not sure is bad...we'll see what happens.

Also, I'm contemplating looking into a way to add "named data structure" support
to the Archive at a lower level, then allow it to use a nameing system to apply
names to each data structure and then output to any backend that supports
naming, like taf, xml, etc.

1 files changed, 5 insertions, 3 deletions

diff --git a/src/tafnode.h b/src/tafnode.h
index a570d2d..10232d2 100644
--- a/src/tafnode.h
+++ b/src/tafnode.h
@@ -24,11 +24,13 @@ namespace Bu
                 virtual ~TafNode();
 
                 void setName( const Bu::FString &sName );
-                const Bu::FString &getName();
+                const Bu::FString &getName() const;
 
                 void setProperty( Bu::FString sName, Bu::FString sValue );
-                const PropList &getProperty( const Bu::FString &sName );
-                const NodeList &getNode( const Bu::FString &sName );
+                const Bu::FString &getProperty( const Bu::FString &sName ) const;
+                const TafNode *getNode( const Bu::FString &sName ) const;
+                const PropList &getProperties( const Bu::FString &sName ) const;
+                const NodeList &getNodes( const Bu::FString &sName ) const;
                 void addChild( TafNode *pNode );
 
         private: