Skip site navigation (1) Skip section navigation (2)

Re: Cannot

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cannot
Date: 2011-10-26 21:15:30
Message-ID: 0EA7B34A-AA16-4611-8AA6-D399B0028939@kineticode.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Oct 26, 2011, at 2:06 PM, Andrew Dunstan wrote:

>> Suggested doc “patch”:
>> 
>>     grep -lri 'can not' doc | xargs perl -i -pe 's/can not/cannot/g'
> 
> Why? "can not" is perfectly grammatical AFAIK.

True, but there's a logic issue. Take this example from doc/src/sgml/func.sgml:

>    <para>
>      <function>pg_advisory_xact_lock</> works the same as
>      <function>pg_advisory_lock</>, expect the lock is automatically released
>      at the end of the current transaction and can not be released explicitly.
>     </para>

I read this as equivalent to "can be not released." Which of course is silly, so as I read it I realize what it means, but it trips up my overly logical brain. It interrupts the flow. There is no such confusion in "cannot be released" and thus no tripping up on meaning.

Best,

David

In response to

  • Re: Cannot at 2011-10-26 21:06:12 from Andrew Dunstan

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2011-10-26 21:20:48
Subject: Re: Cannot
Previous:From: Andrew DunstanDate: 2011-10-26 21:06:12
Subject: Re: Cannot

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group