Re: Incompatibility of CC mode

[Masatake YAMATO]

> Is there any good reason for this incompatibility?
> If not, let's get rid of it.
> 
> ------- Start of forwarded message -------
> X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY 
>       autolearn=failed version=3.1.0
> DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
>       
> h=domainkey-signature:received:received:mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer;
>       
> b=dTIuFhXeJa1XzScGibBwsvdZozFDIredsI5PPbrUpWmgu46kECkDaB39BkotrBhmcTA1bfRnZsfRJRW43M0hcxmZsOK961kXDmqGSofe63dYoQ60HNZ9Ps43xDen9/w/blSp7/yvJSIP9APBajtKPsf9e9WypGhd4pqBpiNBRD8=
> Mime-Version: 1.0 (Apple Message framework v752.3)
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
> To: address@hidden
> From: Paul Curry <address@hidden>
> Date: Mon, 2 Apr 2007 15:46:32 -0500
> Subject: c-subword-mode - inconsistent behavior
> 
> The functions c-capitalize-subword, c-downcase-subword, c-upcase-subword
> claim to behave like their normal emacs counterparts, but all three
> functions move the point when given a negative argument.  Furthermore,
> c-capitalize-subword doesn't even work with a negative argument on my
> machine.  I changed the functions to better mimic the behavior of
> capitalize/downcase/upcase/-word: they no longer move point with a  
> negative
> argument.

It seems that Paul's argument is correct.
I will review Paul's version of code.

Masatake YAMATO