r181071 - [Doc parsing] Provide diagnostics for unknown documentation

[Douglas Gregor]

Sent from my iPhone

On May 3, 2013, at 5:12 PM, Dmitri Gribenko <gribozavr at gmail.com> wrote:

> On Sat, May 4, 2013 at 3:10 AM, jahanian <fjahanian at apple.com> wrote:
>> 
>> On May 3, 2013, at 5:07 PM, Dmitri Gribenko <gribozavr at gmail.com> wrote:
>> 
>>> On Sat, May 4, 2013 at 3:02 AM, jahanian <fjahanian at apple.com> wrote:
>>>> Yes, there will be a typo correction coming (it is part of above radar).
>>> 
>>> This is a weird suggestion (there are no other warnings like that),
>> 
>> I don't understand. Which suggestion is weird :)?
> 
> This one below.  It is weird because I don't think we have any
> warnings that disappear because we don't have a good typo correction.

We have a cutoff with normal typo correction, ie, we don't correct if our edit distance is greater than 1/3 of the length of the typed identifier. I think it's a great idea to simply use a tighter bound here (say, only allowing one or two-character typos).  

>>> but anyway: we could emit this diagnostic by default only if we have a
>>> very good correction.
> 
> Dmitri
> 
> --
> main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
> (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits