>sorry, i meant: see getfields, tokenize, etc. instead of strtok i ought to have included an explanation, but i was short of time. the biggest problem is that strtok keeps some hidden state between calls, so it's a nuisance in concurrent programming. i usually find having the result as an array of strings more helpful than having to make several calls, as well.
probably POSIX has fixed the concurrency problem by implying thread-local storage for strtok's state (thus creating a different problem elsewhere) tokenize is often useful because it handles quoting, which is useful for space-separated fields that need to be able to contain white space.
