2 options
Grammaticalisation paths of 'Have' in English / Andrzej M. Łęcki.
- Format:
- Book
- Author/Creator:
- Łęcki, Andrzej M.
- Series:
- Studies in English medieval language and literature ; Bd. 24.
- Studies in English medieval language and literature, 1436-7521 ; v. 24
- Language:
- English
- Subjects (All):
- Grammar, Comparative and general--Grammaticalization.
- Grammar, Comparative and general.
- English language--Verb phrase.
- English language.
- Physical Description:
- 1 online resource (xi, 269 pages) : illustrations.
- Place of Publication:
- Frankfurt am Main ; Oxford : Peter Lang, [2010]
- System Details:
- text file
- Summary:
- Lecki (linguistics, Pedagogical U. of Cracow, Poland) explores the emergence of the verb have in English through the lens of grammaticalization theory, arguing that the grammatical emergence of have occurred sequentially through pragmatic-semantic, morphosyntactic, and phonetic changes. He also addresses a relatively neglected issue in the field by describing the development of the had better structure and of the causative have. Annotation ©2011 Book News, Inc., Portland, OR (booknews.com)
- Contents:
- Chapter 1 Grammaticalization theory
- 1 Introduction 1
- 2 The history of grammaticalisation 3
- 2.1 From syntax to morphology - Givón 4
- 2.2 Cologne project 5
- 2.2.1 Lehmann's analysis 6
- 2.2.2 Heine and Reh's analysis 10
- 2.3 Hopper's proposals 11
- 2.4 Traugott's pragmatic approach 18
- 3 Recent studies on grammaticalisation 20
- 4 The term grammaticalisation 22
- 5 Motivation for and mechanisms of grammaticalisation 25
- 5.1 Morphosyntactic changes 28
- 5.2 Pragmatic-semantic changes 29
- 5.2.1 Semantic content - a gain or loss? 29
- 5.2.2 Metaphorisation - metonymisation vs. analogy - reanalysis 31
- 5.3 Phonetic changes 34
- 5.4 Gradualness 36
- 6 Unidirectionality hypothesis and its criticism 37
- 7 Clines and paths of grammatical change 41
- 8 Criticism of grammaticalisation 44
- Chapter 2 Semanticisation of HAVE
- 1 Chapter outline 49
- 2 Earliest phonological development of HAVE 49
- 3 Desemanticisation of HAVE 52
- 3.1 Is there bread? It hasn't. Some cross-linguistic evidence 64
- 3.2 The rise of the HAD BETTER structure 69
- 4 Summary and conclusion 78
- Chapter 3 Along the possession-to-obligation cline
- 1 Introduction 79
- 2 Synchronic characteristics of HAVE TO 81
- 3 Traditional accounts of the development of HAVE TO 86
- 4 The rise of HAVE TO viewed as a syntactically driven change 91
- 5 Grammaticalisation of HAVE TO revised 99
- 5.1 The auxiliary status of HAVE TO in Old English 101
- 5.2 Latin influence 114
- 5.3 Word order of HAVE + to-infinitive 118
- 5.4 Pragmatic-semantic development of HAVE TO 128
- 5.5 Negation of HAVE TO 131
- 5.6 Discussion 134
- 6 (HAVE) GOT TO 138
- 7 Summary 143
- Chapter 4 Possessive Perfect
- 4.1 Chapter outline 145
- 4.2 Traditional views on the rise of possessive perfect 145
- 4.3 The rise of 'have'-perfect in English 149
- 4.3.1 Stages of the development 149
- 4.3.2 AGAN + past participle 155
- 4.3.3 BEON vs. HABBAN + past participle 156
- 4.4 Functions and status of HABBAN + PPP in Old English 164
- 4.4.1 Some differences between OE and PDE perfect 164
- 4.4.2 The level of grammaticalisation of HABBAN + PPP structure 167
- 4.4.3 Similarities between Old and Present-Day English perfect 174
- 4.4.4 Carey's (1994), (1995) analyses 178
- 4.4.5 Perfect infinitive in Old English 184
- 4.5 Causative HAVE 188
- 4.6 Summary 204.
- Notes:
- Description based on print version record.
- Includes bibliographical references (pages 233-259) and indexes.
- Electronic reproduction. Palo Alto, Calif. Available via World Wide Web.
- Local Notes:
- Acquired for the Penn Libraries with assistance from the Constance L. Rosenthal Book Fund.
- ISBN:
- 3653002885
- 9783653002881
- Publisher Number:
- 99951267270
- Access Restriction:
- Restricted for use by site license.
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.