I see it differently. The same command with essentially the same data (except for the one trailing cr) returns different results. The FILTER command works with lines. It doesn't know from squat whether or not the developer meant to "terminate" or "delimit" and simply forgot to "terminate" the last line. In fact I am not even sure I understand the distinction. In this context "terminate" and "delimit" mean the same thing. There is no termination in LC that I know of.
Bob On Feb 21, 2012, at 7:14 AM, Ben Rubinstein wrote: > On 21/02/2012 00:11, Bob Sneidar wrote: >> That is possible. The craziness is that the trailing cr affects the result >> even if the filtered text does not include the last line of the list. If >> there is a trailing cr, then the result will end with a cr no matter WHICH >> lines end up in the filtered text. If there isn't, then the result will NOT >> contain the trailing cr. That cannot be the desired behavior. Anyway, I have >> submitted a QCC on it, but it's too low a level for anyone to worry about I >> suspect. > > That doesn't seem unreasonable to me. > > If you have a list in which the format is that every line including the last > has a terminating return, then filter honours that format in the list it > returns, regardless of which lines were in- or excluded. If you have a list > in which the format is returns delimiting between lines, rather than > terminating each line, then filter honours that. > > I'd read it as a feature. > > Ben > > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
