For speed it is just one single loop. The test for the separation character occurs - besides the check for every next byte - 5 extra times when looking ahead, e.g. after an escape character or a quotation character. Splitting the test out of the loop currently is difficult.
The code is littered with multi-line macros, and I do not think they are awful at all. They work also on all old compilers, and as I am the maintainer, there is no one else that will see them. When digging through perl5 core code, one gets used to multi-line macros. It doesn't bother me.
I will have another look at the approach salva suggested and see if I can improve speed there. Having also $paid work, that will not finish this week though.
FWIW all feedback here warmly welcomed and appreciated, even if I might not agree on some
In reply to Re^3: Speeds vs functionality
by Tux
in thread Speeds vs functionality
by Tux
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |