Yes, agree that applies in all instances (although if using Native format in BCP it does at least fail with a half-useful message).
What was in my mind was CSV with embedded commas, or quoted-data that has embedded commas, or a line-break (regardless of whether quoting is correct) which tends to fail.
Even in systems with tight specs and "straightforward" requirements I've known them run fine for years and then all-of-a-sudden some rogue characters creeps into the data ... and mucks up the TEXT transfer file.
Pity the person that invented CSV didn't choose a binary or escaped format instead. heck .. or even a markup-format