JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for WORDGRAMMAR Archives


WORDGRAMMAR Archives

WORDGRAMMAR Archives


WORDGRAMMAR@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

WORDGRAMMAR Home

WORDGRAMMAR Home

WORDGRAMMAR  2000

WORDGRAMMAR 2000

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

RE: invisible doohickeys

From:

"And Rosta" <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Mon, 3 Jan 2000 19:12:54 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (49 lines)

Jasp:
> And:
> 
> > I understand your & Nik's & others' disquiet at the existence of
> > null words, since they definitely relax restrictions on the set
> > of grammars that the theory can express. However, I gave an 
> > argument in an earlier message that even before you consider
> > any actual data, if you think about how language must work, 
> > you're forced to the conclusion that in principle some null 
> > words must be able to exist, unless you can find some 
> > nonmetatheoretical reason for excluding them.
> 
> I agre entirely. We have no trouble in allowing _agre_ to bea 
> AGREE, even though it doesn't have one of the _e_s. Then we 
> should be very surprised if there weren't sometimes cases where 
> the whole form was missing.

But this is a different kind of example. The grammar says the form is
/agree/, but when that gets interpreted at the phonetic interface we
will under certain circumstances accept [agr] or even [] as a valid
interpretation of /agree/. This is different from the grammar itself
saying that // is a valid form of AGREE.

I'm delighted to be agreed with, though. 

And btw, I didn't even notice the <agre> in the first sentence on first
reading.

> It is for this reason that I favour your position (&), that null words 
> are whatever word they have to be less the form, rather than PRO. I 
> should point out, though, that I'm not convinced by your argument 
> that it's too unlikely that a lexeme with the form // should have the 
> proeprties Dick wants to give to PRO: it's no more unlikely than 
> that a lexeme with the form /kat/ should mean 'cat'.

So would you claim that there is an equal probability of CAT having the
form // and PRO having the form /kat/?

No, my dear Watson, the phonologylessness of PRO is far far too convenient
and neat an alibi...

[I'm afraid I momentarily usurped your Holmeshood there.]


--And.


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
June 2021
October 2020
April 2020
March 2020
September 2019
June 2019
May 2019
April 2019
December 2018
September 2018
August 2018
July 2018
June 2018
April 2018
June 2017
April 2017
March 2017
February 2017
January 2017
December 2016
September 2016
August 2016
July 2016
June 2016
February 2016
November 2015
July 2015
April 2015
March 2015
February 2015
September 2014
August 2014
July 2014
June 2014
May 2014
March 2014
February 2014
October 2013
July 2013
June 2013
April 2013
March 2013
February 2013
January 2013
February 2012
February 2011
January 2011
June 2010
April 2010
March 2010
December 2009
August 2009
June 2009
April 2009
March 2009
February 2009
November 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
December 2007
October 2007
September 2007
August 2007
July 2007
June 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager