<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: To be anticipated</title>
	<atom:link href="http://languagelog.ldc.upenn.edu/nll/?feed=rss2&#038;p=3932" rel="self" type="application/rss+xml" />
	<link>http://languagelog.ldc.upenn.edu/nll/?p=3932</link>
	<description></description>
	<pubDate>Sun, 19 May 2013 20:43:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Jonathan Gress-Wright</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-194328</link>
		<dc:creator>Jonathan Gress-Wright</dc:creator>
		<pubDate>Tue, 08 May 2012 18:32:48 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-194328</guid>
		<description>The conversation about "passive voice" and prescriptivism on the part of professional linguists reminds me of Conquest's Law (named after the reactionary historian Robert Conquest): Everyone is a reactionary in the subject he knows about.</description>
		<content:encoded><![CDATA[<p>The conversation about "passive voice" and prescriptivism on the part of professional linguists reminds me of Conquest's Law (named after the reactionary historian Robert Conquest): Everyone is a reactionary in the subject he knows about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jo</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-194317</link>
		<dc:creator>Jo</dc:creator>
		<pubDate>Tue, 08 May 2012 18:06:08 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-194317</guid>
		<description>It strikes me that quoting Darwin in support of anything isn't going to have much weight with Neanderthals.</description>
		<content:encoded><![CDATA[<p>It strikes me that quoting Darwin in support of anything isn't going to have much weight with Neanderthals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193816</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 06 May 2012 12:40:21 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193816</guid>
		<description>With respect to the use of "passive", the problem is that would‐be dispensers of writing proscriptions use it the way that people like Deepak Chopra use the word "quantum". They rely on its status as a technical term to convey a sense of authority and expertise that they do not in fact possess. Peddlers of woo writing advice rely on the prestige of real linguistic description and its associated terminology, just as peddlers of woo medicine rely on the prestige of physics or biology. That, to me, is the major reason that the widespread misuse of "passive" as a technical term is a problem.</description>
		<content:encoded><![CDATA[<p>With respect to the use of "passive", the problem is that would‐be dispensers of writing proscriptions use it the way that people like Deepak Chopra use the word "quantum". They rely on its status as a technical term to convey a sense of authority and expertise that they do not in fact possess. Peddlers of woo writing advice rely on the prestige of real linguistic description and its associated terminology, just as peddlers of woo medicine rely on the prestige of physics or biology. That, to me, is the major reason that the widespread misuse of "passive" as a technical term is a problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: W. Kiernan</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193769</link>
		<dc:creator>W. Kiernan</dc:creator>
		<pubDate>Sun, 06 May 2012 01:41:43 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193769</guid>
		<description>Maybe Chomsky actually meant "anticipated" rather than "expected";  that is, not only expected, but prepared-for with counterarguments ("I'll tell you why they shouldn't go away and leave us alone!").</description>
		<content:encoded><![CDATA[<p>Maybe Chomsky actually meant "anticipated" rather than "expected";  that is, not only expected, but prepared-for with counterarguments ("I'll tell you why they shouldn't go away and leave us alone!").</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Hemmens</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193760</link>
		<dc:creator>Dan Hemmens</dc:creator>
		<pubDate>Sat, 05 May 2012 23:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193760</guid>
		<description>&lt;blockquote&gt;So it seems to have happened with "passive": the metaphorical meaning ("weak") reverted to a literal one misapplied by ignorant teachers and editors.&lt;/blockquote&gt;

I think the problem is somewhat muddied here by the fact the non-technical (or perhaps we should call it quasi-technical) use of "passive" is very, very inconsistent. As Andrew (not the same one) points out, some people think that a passive clause is any clause with a form of the verb "to be" in it. Others think that "the passive voice" is any form of expression that is vague about agency (or indeed that fails to place blame where the complainant feels it should be placed). Still others think that "the passive voice" means anything that is in any way weak.

To put it another way, the problem with the "non-technical" definition of "passive voice" is that it only makes any sense at *all* if you mistakenly believe it to be the real, technical definition. The popular uses all claim to identify a particular way of using English, when they don't. When people say that a particular passage "avoids agency by using the passive voice" they clearly think that there is some particular type of language being used and that they are able to identify it.

Context is also important here. "Passive voice" is very different to "gridlock" in the sense that it isn't a word people use casually, rather it's a technical term that people attempt to use in technical analysis.

Perhaps a better analogy than "gridlock" would be "quantum" or possibly "genetic". "Genetic" has a very specific meaning in biology (it means, well, literally encoded in DNA) but tends to get used in everyday speech as a synonym for "hereditary" or "predetermined". This is all well and good, but once people start trying to make actual testable claims about the physical world that rely on pretending that the pop-culture definition is the same as the scientific definition (like, say, in pretty much every newspaper article about genetics you'll ever read), you really do have to sit down and say "no, you are using that word wrong". Which is really a shorthand for saying "you appear to be assuming that your understanding of a metaphorical idea which, confusingly, has the same name as a real scientific concept, is the same as understanding the scientific concept itself and you are now making false claims about an area of science you do not understand."

It is perfectly fine for people to use "passive" to mean "vague about agency" or "weak" or "contains a form of the word to be" but if those are the definitions you're using, you can't pass your comments of as an actual analysis of the language, any more than you can pass off your observation that you and your dad both like the same kinds of books as an actual analysis of the biochemistry.</description>
		<content:encoded><![CDATA[<blockquote><p>So it seems to have happened with "passive": the metaphorical meaning ("weak") reverted to a literal one misapplied by ignorant teachers and editors.</p></blockquote>
<p>I think the problem is somewhat muddied here by the fact the non-technical (or perhaps we should call it quasi-technical) use of "passive" is very, very inconsistent. As Andrew (not the same one) points out, some people think that a passive clause is any clause with a form of the verb "to be" in it. Others think that "the passive voice" is any form of expression that is vague about agency (or indeed that fails to place blame where the complainant feels it should be placed). Still others think that "the passive voice" means anything that is in any way weak.</p>
<p>To put it another way, the problem with the "non-technical" definition of "passive voice" is that it only makes any sense at *all* if you mistakenly believe it to be the real, technical definition. The popular uses all claim to identify a particular way of using English, when they don't. When people say that a particular passage "avoids agency by using the passive voice" they clearly think that there is some particular type of language being used and that they are able to identify it.</p>
<p>Context is also important here. "Passive voice" is very different to "gridlock" in the sense that it isn't a word people use casually, rather it's a technical term that people attempt to use in technical analysis.</p>
<p>Perhaps a better analogy than "gridlock" would be "quantum" or possibly "genetic". "Genetic" has a very specific meaning in biology (it means, well, literally encoded in DNA) but tends to get used in everyday speech as a synonym for "hereditary" or "predetermined". This is all well and good, but once people start trying to make actual testable claims about the physical world that rely on pretending that the pop-culture definition is the same as the scientific definition (like, say, in pretty much every newspaper article about genetics you'll ever read), you really do have to sit down and say "no, you are using that word wrong". Which is really a shorthand for saying "you appear to be assuming that your understanding of a metaphorical idea which, confusingly, has the same name as a real scientific concept, is the same as understanding the scientific concept itself and you are now making false claims about an area of science you do not understand."</p>
<p>It is perfectly fine for people to use "passive" to mean "vague about agency" or "weak" or "contains a form of the word to be" but if those are the definitions you're using, you can't pass your comments of as an actual analysis of the language, any more than you can pass off your observation that you and your dad both like the same kinds of books as an actual analysis of the biochemistry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joanne salton</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193729</link>
		<dc:creator>joanne salton</dc:creator>
		<pubDate>Sat, 05 May 2012 20:49:03 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193729</guid>
		<description>My point is though that it rather seems to give the impression when you cite Dickens that if Dickens wrote something then it must necessarily be good current English. Indeed, one previous poster with a descriptive viewpoint took exactly that view and laughed at the prescriptivists for suggesting that something found in the great Dickens might possibly not be acceptable. Thus while it is a reasonable way to convince people that they are wrong about such-and-such a usage being a new and ignorant mistake, this (rather common) response always reinforces the mistaken view that authority is key, not usage.

&lt;font color="#FF0000"&gt;[(myl) In this kind of discussion, there's a big difference between an appeal to authority of the form "Strunk (or Fowler or Ayres or ...) said you must always (or never) do X", and an appeal to authority of the form "Dickens (or Carlyle or Austen or Eliot or Yeats...) routinely employed construction or usage X". The first is the prescription of a self-appointed authority; the second is a description of the practice of well-regarded writers.

In relation to such descriptions of practice, it's certainly in order to consider the time period. But when we have a usage that's been common among well-regarded writers for several hundred years, prescriptive advice against it is especially unlikely to be valid.

I could have cited Alice Munro's 1977 &lt;em&gt;The Moons of Jupiter&lt;/em&gt;:

&lt;p style="padding-left: 30px;"&gt; Iris's lipstick, her bright teased hair, her iridescent dress and oversized brooch, her voice and conversation, were all part of a policy &lt;strong&gt;which&lt;/strong&gt; was not a bad one: she was in favor of movement, noise, change, flashiness, hilarity, and courage.&lt;/p&gt;

...or countless other recent works by living authors. But a common response is to take such citations as evidence of failure to maintain standards.]&lt;/font&gt;


</description>
		<content:encoded><![CDATA[<p>My point is though that it rather seems to give the impression when you cite Dickens that if Dickens wrote something then it must necessarily be good current English. Indeed, one previous poster with a descriptive viewpoint took exactly that view and laughed at the prescriptivists for suggesting that something found in the great Dickens might possibly not be acceptable. Thus while it is a reasonable way to convince people that they are wrong about such-and-such a usage being a new and ignorant mistake, this (rather common) response always reinforces the mistaken view that authority is key, not usage.</p>
<p><font color="#FF0000">[(myl) In this kind of discussion, there's a big difference between an appeal to authority of the form "Strunk (or Fowler or Ayres or &#8230;) said you must always (or never) do X", and an appeal to authority of the form "Dickens (or Carlyle or Austen or Eliot or Yeats&#8230;) routinely employed construction or usage X". The first is the prescription of a self-appointed authority; the second is a description of the practice of well-regarded writers.</p>
<p>In relation to such descriptions of practice, it's certainly in order to consider the time period. But when we have a usage that's been common among well-regarded writers for several hundred years, prescriptive advice against it is especially unlikely to be valid.</p>
<p>I could have cited Alice Munro's 1977 <em>The Moons of Jupiter</em>:</p>
<p style="padding-left: 30px;"> Iris's lipstick, her bright teased hair, her iridescent dress and oversized brooch, her voice and conversation, were all part of a policy <strong>which</strong> was not a bad one: she was in favor of movement, noise, change, flashiness, hilarity, and courage.</p>
<p>&#8230;or countless other recent works by living authors. But a common response is to take such citations as evidence of failure to maintain standards.]</font></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew (not the same one)</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193564</link>
		<dc:creator>Andrew (not the same one)</dc:creator>
		<pubDate>Fri, 04 May 2012 19:09:32 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193564</guid>
		<description>I honestly don't know who I'm not the same one as. I adopted the name in one thread where another Andrew had posted before me, and then kept it so as to have a consistent identity, since there are lots of Andrews about.</description>
		<content:encoded><![CDATA[<p>I honestly don't know who I'm not the same one as. I adopted the name in one thread where another Andrew had posted before me, and then kept it so as to have a consistent identity, since there are lots of Andrews about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coby Lubliner</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193535</link>
		<dc:creator>Coby Lubliner</dc:creator>
		<pubDate>Fri, 04 May 2012 16:48:04 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193535</guid>
		<description>Andrew (not the same one) [not the same one as who?]: I hope you're right -- I personally don't like to see technical terms misused  -- but if the examples cited by the LL folk are any indication, the line seems to have been crossed. The case is similar to "gridlock": from a technical meaning (traffic blocking intersections in a street grid) to a metaphorical one ("legislative gridlock") back to an inaccurate literal one. So it seems to have happened with "passive": the metaphorical meaning ("weak") reverted to a literal one misapplied by ignorant teachers and editors. 
I might have suggested that grammarians abandon the term "passive" to the laity and replace it with, say, the Greek equivalent, but that would be... pathetic (παθητική)!</description>
		<content:encoded><![CDATA[<p>Andrew (not the same one) [not the same one as who?]: I hope you're right &#8212; I personally don't like to see technical terms misused  &#8212; but if the examples cited by the LL folk are any indication, the line seems to have been crossed. The case is similar to "gridlock": from a technical meaning (traffic blocking intersections in a street grid) to a metaphorical one ("legislative gridlock") back to an inaccurate literal one. So it seems to have happened with "passive": the metaphorical meaning ("weak") reverted to a literal one misapplied by ignorant teachers and editors.<br />
I might have suggested that grammarians abandon the term "passive" to the laity and replace it with, say, the Greek equivalent, but that would be&#8230; pathetic (παθητική)!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew (not the same one)</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193515</link>
		<dc:creator>Andrew (not the same one)</dc:creator>
		<pubDate>Fri, 04 May 2012 15:27:27 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193515</guid>
		<description>Coby Lubliner: I totally agree with you about 'grammar' and 'linguist', but I would say that 'passive voice' is a different matter. Most people who use that expression, so far as I can see, think they are referring to a grammatical form, while being quite unclear as to what that form is. Some, for instance, think that any sentence including the word 'is' is in the passive voice. If the term really has simply acquired a new, non-technical sense, then I agree no one has a right to complain. But it seems to me this hasn't happened yet. There is, I guess, sometimes a fuzzy line between the misuse of a technical term and development of a new sense, but I don't think it has been crossed yet.</description>
		<content:encoded><![CDATA[<p>Coby Lubliner: I totally agree with you about 'grammar' and 'linguist', but I would say that 'passive voice' is a different matter. Most people who use that expression, so far as I can see, think they are referring to a grammatical form, while being quite unclear as to what that form is. Some, for instance, think that any sentence including the word 'is' is in the passive voice. If the term really has simply acquired a new, non-technical sense, then I agree no one has a right to complain. But it seems to me this hasn't happened yet. There is, I guess, sometimes a fuzzy line between the misuse of a technical term and development of a new sense, but I don't think it has been crossed yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: This Week&#8217;s Language Blog Roundup &#124; Wordnik</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193504</link>
		<dc:creator>This Week&#8217;s Language Blog Roundup &#124; Wordnik</dc:creator>
		<pubDate>Fri, 04 May 2012 14:15:29 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193504</guid>
		<description>[...] Victor Mair examined a new non-stigmatizing Chinese word for epilepsy; and Mark Liberman considered Noam Chomsky and anticipation. Geoff Pullum discussed ongoing lexical fascism, a couple of rare words, and at Lingua Franca, the [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Victor Mair examined a new non-stigmatizing Chinese word for epilepsy; and Mark Liberman considered Noam Chomsky and anticipation. Geoff Pullum discussed ongoing lexical fascism, a couple of rare words, and at Lingua Franca, the [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joanne Salton</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193482</link>
		<dc:creator>Joanne Salton</dc:creator>
		<pubDate>Fri, 04 May 2012 10:29:35 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193482</guid>
		<description>I sometimes wonder why people are so keen to play strong prescriptivists at their own game by citing Dickens etc.

Surely it matters little what was said/written in previous centuries, if we adopt a descriptive viewpoint.

&lt;font color="#FF0000"&gt;[(myl) Surely the reason is obvious. It's trivial to find current examples of &lt;i&gt;anticipate&lt;/i&gt; used in the sense forbidden by the Telegraph's style guide -- just search Google Books or any newspaper index for e.g. "anticipate that", and you'll find as many as you like. The expected rebuttal, especially from self-described "conservative" sources, is that this is just a symptom of modern linguistic and cultural degeneracy, we need to keep up standards, etc. So it's useful to point out that the usage in question is not some modern error, but has been common in elite writing for a couple of centuries.]&lt;/font&gt;
</description>
		<content:encoded><![CDATA[<p>I sometimes wonder why people are so keen to play strong prescriptivists at their own game by citing Dickens etc.</p>
<p>Surely it matters little what was said/written in previous centuries, if we adopt a descriptive viewpoint.</p>
<p><font color="#FF0000">[(myl) Surely the reason is obvious. It's trivial to find current examples of <i>anticipate</i> used in the sense forbidden by the Telegraph's style guide &#8212; just search Google Books or any newspaper index for e.g. "anticipate that", and you'll find as many as you like. The expected rebuttal, especially from self-described "conservative" sources, is that this is just a symptom of modern linguistic and cultural degeneracy, we need to keep up standards, etc. So it's useful to point out that the usage in question is not some modern error, but has been common in elite writing for a couple of centuries.]</font></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Saylor</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193480</link>
		<dc:creator>Tom Saylor</dc:creator>
		<pubDate>Fri, 04 May 2012 09:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193480</guid>
		<description>TSG: 

I wonder what the Telegraph Style Guide has to say about 'unanticipated', which apparently has been in use since the 18th century. Does it insist that the word is properly applied only to an expected event that has not been acted upon in advance, e.g., a trip to Africa or a marriage for which no preparations have been made? I don't think I've ever seen the adjective used in that sense.

The TSG's implicit prescription (it doesn't explicitly prescribe or proscribe any verbal behavior here--doesn't explicitly say one should not use 'anticipate' in this way) is not worth following, but I don't think it's prescriptivist poppycock--if by 'poppycock' we mean a claim that is wildly false. Prescriptions (deontic statements) are neither true nor false. No, the TSG's observation about 'anticipate' is descriptivist poppycock, pure and simple.</description>
		<content:encoded><![CDATA[<p>TSG: </p>
<p>I wonder what the Telegraph Style Guide has to say about 'unanticipated', which apparently has been in use since the 18th century. Does it insist that the word is properly applied only to an expected event that has not been acted upon in advance, e.g., a trip to Africa or a marriage for which no preparations have been made? I don't think I've ever seen the adjective used in that sense.</p>
<p>The TSG's implicit prescription (it doesn't explicitly prescribe or proscribe any verbal behavior here&#8211;doesn't explicitly say one should not use 'anticipate' in this way) is not worth following, but I don't think it's prescriptivist poppycock&#8211;if by 'poppycock' we mean a claim that is wildly false. Prescriptions (deontic statements) are neither true nor false. No, the TSG's observation about 'anticipate' is descriptivist poppycock, pure and simple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan H</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193475</link>
		<dc:creator>Dan H</dc:creator>
		<pubDate>Fri, 04 May 2012 08:57:09 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193475</guid>
		<description>I agree with those who, formal definitions aside, find "that's to be anticipated" to sound odd. I'm struggling to put my finger on *why*, however.</description>
		<content:encoded><![CDATA[<p>I agree with those who, formal definitions aside, find "that's to be anticipated" to sound odd. I'm struggling to put my finger on *why*, however.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J. Goard</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193461</link>
		<dc:creator>J. Goard</dc:creator>
		<pubDate>Fri, 04 May 2012 06:16:23 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193461</guid>
		<description>&lt;i&gt;Expect&lt;/i&gt; is one of the words that frustrates me the most in the English used by the Korean speakers around me, because of the sense of entitlement it attributes to its subject whenever its complement involves some kind of voluntary action on the part of another person. So, whether the complement is an infinitive clause with unexpressed subject coreferential with the matrix subject (1) or is a distinct subject (2), or is a nominal (3), I'm challenged to distinguish the perfectly fine (a) sentences with the (b) sentences where using &lt;i&gt;expect&lt;/i&gt; will make you come across as a jerk:

(1) a. I expect to have a lot of fun this summer.
b. # I expect to have a lot of fun at your party.
(2) a. I expect the economy to recover quickly.
b. # I expect you to recover from your cancer.
(3) a. I expect a lot more rain in Ohio this year.
b. # I expect a lot more sexual assaults in Ohio this year.

&lt;i&gt;Anticipate&lt;/i&gt; (though it doesn't take an infinitival complement) at least avoids this subtle but potentially critical pragmatic problem. These days, I reflexively prefer it (or a whole host of other constructions) to &lt;i&gt;expect&lt;/i&gt;.</description>
		<content:encoded><![CDATA[<p><i>Expect</i> is one of the words that frustrates me the most in the English used by the Korean speakers around me, because of the sense of entitlement it attributes to its subject whenever its complement involves some kind of voluntary action on the part of another person. So, whether the complement is an infinitive clause with unexpressed subject coreferential with the matrix subject (1) or is a distinct subject (2), or is a nominal (3), I'm challenged to distinguish the perfectly fine (a) sentences with the (b) sentences where using <i>expect</i> will make you come across as a jerk:</p>
<p>(1) a. I expect to have a lot of fun this summer.<br />
b. # I expect to have a lot of fun at your party.<br />
(2) a. I expect the economy to recover quickly.<br />
b. # I expect you to recover from your cancer.<br />
(3) a. I expect a lot more rain in Ohio this year.<br />
b. # I expect a lot more sexual assaults in Ohio this year.</p>
<p><i>Anticipate</i> (though it doesn't take an infinitival complement) at least avoids this subtle but potentially critical pragmatic problem. These days, I reflexively prefer it (or a whole host of other constructions) to <i>expect</i>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Briggs</title>
		<link>http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193455</link>
		<dc:creator>Michael Briggs</dc:creator>
		<pubDate>Fri, 04 May 2012 03:45:32 +0000</pubDate>
		<guid isPermaLink="false">http://languagelog.ldc.upenn.edu/nll/?p=3932#comment-193455</guid>
		<description>And wooden buildings, I guess, are never dilapidated.</description>
		<content:encoded><![CDATA[<p>And wooden buildings, I guess, are never dilapidated.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
