And the best cure for a comma splice is almost always a semi-colon; at least temporarily, as expressing what the writer was trying to get at.
'don't write unnecessarily long and complicated sentences' |
|
And the essential part of that sentence is "unnecessarily"...
Since semi-colons do facilitate the writing of unnecessarily long and complicated sentences, it's easy to see why they get the blame. |
|
Along with "was" and "that" and "had" and so on being blamed for bad writing when it's not them at all - it's various kinds of bad in which they're innocently implicated. It's like blaming the canary in the mine for the gas explosion.
<Added>"To err is human; to forgive, divine."
Is perhaps another example of why rules aren't rules, they're conventions. In the normal, ordinary conventions, both sides of a semi-colon joiner-divider should be grammatically finite sentences, and the second half of that one isn't.
It's not "correct", but it's absolutely right; that's why it's one of the great sentences in the language.
<Added>IT is very nearly correct, mind you - or maybe it is in some refinement of grammar that I'd need David Crystal's £100 book to look up:
The comma after "forgive" is a gapping comma, which is the sort which goes where the omitted word is.
In this case the omitted word is "is", which is the main verb - so we hear a second "is" in that second half - and the sentence becomes complete. Divine, in other words.
I do love it when form follows function.