Thanks, guys! Always a big help. My overheated benchmarks show that the chars() function is the winner by as much as a 24% margin.
Thanks, Buzz, for the reminder about .ref. In my application, however, I'm hardly doing any multiple accesses of the same chunk, so I don't have a strong case for using that property right now. The only reason I threw in the property list version of the two-value return is because it made better visual "code sense" at the re-access point using .h and .v, rather than [1] and [2]. It was clearer what each value was. Still, I'll probably just stick with the simple linear list approach. Faster ands smaller. The values aren't used as a point in the context of Lingo (they represent a location within the SVG coordinate plane), so I'll refrain from incurring the overhead of points. Thanks again! -Christopher [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!]
