Hi Robert, Thanks for the explanation of your reasoning. Looking at the Core guide, paths look purpose-built for this sort of database. So your reasons have good company :^)
Regards, Brett. > Hi, there are several reasons: > > - For storing data I'm always working with nested blocks of name/value > pairs. This has proven to be the best approach yet. My goal is to keep > this "database" as the master of data, the source. To avoid copying around > and to minimize searches in big databases, I always try to work "in place" > by using a reference. > > - Such paths are easy to create programmatically. This code can be used to > access/alter record structures in an abstract way, because I can specify > parts of a path! (including the last part of a path!) by variables. > > - I find it logical in the Rebol context. > > I hope these are good reasons for it :-) Robert -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
