Jump to ContentJump to Main Navigation
Provocative Syntax$
Users without a subscription are not able to see the full content.

Phil Branigan

Print publication date: 2010

Print ISBN-13: 9780262014991

Published to MIT Press Scholarship Online: August 2013

DOI: 10.7551/mitpress/9780262014991.001.0001

Show Summary Details
Page of

PRINTED FROM MIT PRESS SCHOLARSHIP ONLINE (www.mitpress.universitypressscholarship.com). (c) Copyright The MIT Press, 2017. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a monograph in MITSO for personal use (for details see http://www.mitpress.universitypressscholarship.com/page/privacy-policy).date: 12 December 2017

Provoking Trace Deletion

Provoking Trace Deletion

Chapter:
(p.119) 5 Provoking Trace Deletion
Source:
Provocative Syntax
Author(s):

Phil Branigan

Publisher:
The MIT Press
DOI:10.7551/mitpress/9780262014991.003.0005

This chapter shows that a substantial number of “constraints” which restrict movement in, through, and to the left periphery reduce to one general pattern that bars movement from [Spec, Fin] to [Spec, Force]. One special cases of this generalization is the that-trace effect. With this pattern established, the chapter then shows that it reflects a failure to delete intermediate Ā-traces in successive cyclic Ā-movement, and that this failure induces a crash at logical form. The reason such traces must be deleted can only be that they constitute linguistic objects distinct from the other copies in an interpretable, binary, operator-variable chain.

Keywords:   that-trace effects, movement, left periphery, logical form

MIT Press Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs, and if you can't find the answer there, please contact us.