Go with the existing (HyperCard) model and be done with it, says I. What, exactly, is so horribly deficient about HyperCard's existing delimiter-handling methods, that we should even *consider* going berserk with "delimited by" and all the rest of that fancy-schmancy stuff? If we can do *this* -- set the itemDelimiter to [character] put item 7 of ThisVariable into WhatEver -- in standard, generic, comprehensible HyperTalk, why even *bother* trying to shoehorn two easily-understood lines of code down into one semi-opaque line of code? Yes, yes, it's trivially easy to imagine superhypercomplexificationated hypothetical examples which "prove" that multiple delimiters, or whatever other rarefied "features", are good and necessary... but can anyone come up with a *REAL* example, that would be of something approximating *PRACTICAL* utility, to support the contention that HyperCard's existing delimiter-handling features Just Aren't Good Enough? Anyone?
