4 ms·
Won't this give an incorrect number of bytes for several consecutive whitespace characters? Why not using # to count the bytes instead?
by yiyus 7y ago
Won't this give an incorrect number of bytes for several consecutive whitespace characters? Why not using # to count the bytes instead?
- tluyben2 7y agoin k, but with that same bug'; (b:#a;b++/,/a=/:" ";b+#,/a)
- tluyben2 7y agoHere is one without the bug; b:#a;c:,/a=/:" ";(b;b++/c@&~c&=':c;b+#,/a) Now to see if I can check the performance.
- yiyus 7y agoWe discussed this at length in the shakti mailing list [1]. This version by chrispsn is my favorite: {+/["\n"=x],+/[<':~x in "\n\r\t "],#x} I think it's the one that more clearly express the intent. However, this other one by Attila Vrabecz performs better in the current version: {(+/x in"\n\n";+/0>':x in" \n\t\r";#x)}@1:"big.txt" [1] https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/shaktidb/iXpNyAai_x4/3iWWt4rOAQAJ https://groups.google.com/forum/?utm_medium=email&utm_source...
- tluyben2 7y agoNice, thanks for that!