And/or: Difference between revisions

522 bytes added ,  17 August 2016
no edit summary
No edit summary
No edit summary
Line 1: Line 1:
Means “[[or]]”, because “or” includes “[[and]]”.
In a {{nutshell}} “[[and/or]]” means “[[or]]”, because “[[or]]” includes “[[and]]”.


*{{and}}<ref>So Google tells me.</ref> <br>
"And/or" crops up often in mediocre drafting. It has a face only a mother could love. It is borne of the quite unjustified fear that when contemplating a list of alternatives the occurrence of ''any'' of which leads to an certain outcome, one’s plans in that regard might somehow come unstuck if they ''all'' occur. There is no grounds for this fear. Logically, this is how one defines [[and]] and [[or]]:
*{{or}} <ref>ibid.</ref>


It's utterly defeatist drafting, because of the presence of that slash: what does it even mean? That slash admits that the plain, punctuated words of the English language have defeated you.
*{{and}}
*{{or}}
 
And/or is not just ugly; it's defeatist, because of the presence of the [[virgule]], that whoreson slash, which is not even a part of idiomatic punctuation in the English language. It's a decoration. It has no fixed grammatical meaning. That slash admits that the plain, punctuated words of the English language have defeated you.


In fact, that slash means - and can only mean - “[[or]]”. So by saying "and or" you are really saying "and, or or". But to be hermetically sealed and consistent, shouldn't you go the whole hog, and say "and, and/or or"?
In fact, that slash means - and can only mean - “[[or]]”. So by saying "and or" you are really saying "and, or or". But to be hermetically sealed and consistent, shouldn't you go the whole hog, and say "and, and/or or"?
Line 13: Line 15:


{{c2|egg|ISIA}}
{{c2|egg|ISIA}}
<references />