From pycyn@aol.com Tue May 08 03:40:57 2001
Return-Path: <Pycyn@aol.com>
X-Sender: Pycyn@aol.com
X-Apparently-To: lojban@yahoogroups.com
Received: (EGP: mail-7_1_2); 8 May 2001 10:40:57 -0000
Received: (qmail 79340 invoked from network); 8 May 2001 09:30:18 -0000
Received: from unknown (10.1.10.26) by l8.egroups.com with QMQP; 8 May 2001 09:30:18 -0000
Received: from unknown (HELO imo-m04.mx.aol.com) (64.12.136.7) by mta1 with SMTP; 8 May 2001 09:30:18 -0000
Received: from Pycyn@aol.com by imo-m04.mx.aol.com (mail_out_v30.10.) id r.a2.13e88b13 (4529) for <lojban@yahoogroups.com>; Mon, 7 May 2001 18:32:11 -0400 (EDT)
Message-ID: <a2.13e88b13.28287c6a@aol.com>
Date: Mon, 7 May 2001 18:32:10 EDT
Subject: Re: [lojban] imperatives & scope (was: RE: Predicate logic and childhood.)
To: lojban@yahoogroups.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="part1_a2.13e88b13.28287c6a_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10519
From: pycyn@aol.com

--part1_a2.13e88b13.28287c6a_boundary
Content-Type: multipart/alternative;
boundary="part1_a2.13e88b13.28287c6a_alt_boundary"

--part1_a2.13e88b13.28287c6a_alt_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 5/6/2001 8:32:14 AM Central Daylight Time, pycyn@aol.com 
writes:



> <
> 
> >> It does NOT mean (f): 
>> 
>> f. Make it the case that you make a note of my telephone number. 
>> f'. Make it the case that you make a note of a telephone number of mine. 
>> 
>> -- for these would be satisfied if you wrote down any old number but then 
>> took steps to make sure that the phone company assigned this number to me.>
>> 
>> 
> 
> 
> Again, I would use prenex but I suspect that this is common enough that we 
> need a new convention here, as we have already in various other world 
> shiftings, about the referent of definite descriptions therein. since that 
> problem is not completely worked out yet, ... >
> 

In this case however {leca} ought to be enough -- "my current number"



--part1_a2.13e88b13.28287c6a_alt_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><BODY BGCOLOR="#ffffff"><FONT SIZE=2>In a message dated 5/6/2001 8:32:14 AM Central Daylight Time, pycyn@aol.com 
<BR>writes:
<BR>
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&lt;
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">It does NOT mean (f): 
<BR>
<BR> f. &nbsp;Make it the case that you make a note of my telephone number. 
<BR> f'. Make it the case that you make a note of a telephone number of mine. 
<BR>
<BR>-- for these would be satisfied if you wrote down any old number but then 
<BR>took steps to make sure that the phone company assigned this number to me.&gt;
<BR> 
<BR></BLOCKQUOTE>
<BR>
<BR>
<BR>Again, I would use prenex but I suspect that this is common enough that we 
<BR>need a new convention here, as we have already in various other world 
<BR>shiftings, about the referent of definite descriptions therein. &nbsp;since that 
<BR>problem is not completely worked out yet, ... &gt;
<BR></BLOCKQUOTE>
<BR>
<BR>In this case however {leca} ought to be enough -- "my &nbsp;current number"
<BR></BLOCKQUOTE>
<BR></FONT></HTML>

--part1_a2.13e88b13.28287c6a_alt_boundary--

--part1_a2.13e88b13.28287c6a_boundary
Content-Type: message/rfc822
Content-Disposition: inline

Return-path: <Pycyn@aol.com>
From: Pycyn@aol.com
Full-name: Pycyn
Message-ID: <75.1453d2bb.28281db8@aol.com>
Date: Mon, 7 May 2001 11:48:08 EDT
Subject: Re: [lojban] imperatives & scope (was: RE: Predicate logic and childhood.)
To: Pycyn@aol.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part2_a2.13e88b13.28281db8_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10519

--part2_a2.13e88b13.28281db8_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 5/6/2001 8:32:14 AM Central Daylight Time, pycyn@aol.com 
writes:


> 
> >> It does NOT mean (f): 
>> 
>> f. Make it the case that you make a note of my telephone number. 
>> f'. Make it the case that you make a note of a telephone number of mine. 
>> 
>> -- for these would be satisfied if you wrote down any old number but then 
>> took steps to make sure that the phone company assigned this number to me.>
>> 
>> 
> 
> Again, I would use prenex but I suspect that this is common enough that we 
> need a new convention here, as we have already in various other world 
> shiftings, about the referent of definite descriptions therein. since that 
> problem is not completely worked out yet, ... 
> 
In this case however {leca} ought to be enough -- "my current number"


--part2_a2.13e88b13.28281db8_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><BODY BGCOLOR="#ffffff"><FONT SIZE=2>In a message dated 5/6/2001 8:32:14 AM Central Daylight Time, pycyn@aol.com 
<BR>writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">It does NOT mean (f): 
<BR>
<BR> &nbsp;f. &nbsp;Make it the case that you make a note of my telephone number. 
<BR> &nbsp;f'. Make it the case that you make a note of a telephone number of mine. 
<BR>
<BR>-- for these would be satisfied if you wrote down any old number but then 
<BR>took steps to make sure that the phone company assigned this number to me.&gt;
<BR> 
<BR></BLOCKQUOTE>
<BR>
<BR>Again, I would use prenex but I suspect that this is common enough that we 
<BR>need a new convention here, as we have already in various other world 
<BR>shiftings, about the referent of definite descriptions therein. &nbsp;since that 
<BR>problem is not completely worked out yet, ... 
<BR></BLOCKQUOTE>
<BR>In this case however {leca} ought to be enough -- "my &nbsp;current number"
<BR></FONT></HTML>

--part2_a2.13e88b13.28281db8_boundary--

--part1_a2.13e88b13.28287c6a_boundary--

