As far as internal lists are concerned, it would be interesting to compare lingo lists, pregex lists, and vList lists and functions against each other to see if there are any performance gains... Anyone do this already?
~Mathew
Troy Rollins wrote:
On Tuesday, January 27, 2004, at 04:41 AM, Luke wrote:
I'm a big-fan of vList (I think vList members should become a standard generic 'data' type cast member for Director).
If it was, how would you use it differently, or do you already use it now in that way? (Notwithstanding the cool pregEx techniques you described.)
What I'm trying to determine is since I have to do some rework on my project to integrate vList anyway, is there any advantage to taking it deeper and modifying some of my other lists in the project to be using vList - even though I don't really need those lists as external files. This project makes extensive use of lists, including many member.media instances.
Using vList for external files is a no-brainer, that's why you buy it. I honestly had no idea it was a cast member xtra until I started working with it, and then it made me begin to wonder where its place was... as a file format, or as a general list tool in addition. Some of its built-in methods would seem oriented to the latter.
As an example, using propSave xtra, you use Director internal lists, and then call propSave to save the Director list to a file. vList however, has methods to allow it to actually BE the internal list if desired, as well as the ability to behave as a substitute cast file as grimm mentioned.
-- Troy RPSystems, Ltd. http://www.rpsystems.net
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
