Matthew Hughes <matthewhughes934@xxxxxxxxx> writes: > This needs some updates. What does it mean? The patterns that were posted were so broken that they are unusable and harm the users by giving misleading information? Or do the patterns work just fine in basic or tutorial cases, but with more advanced or realistic uses of the language construct, they highlight wrong lines as the function header and/or split at wrong word boundaries that are obviously much less optimal than ideal that any human users would find questionable? In the latter case, how far from the ideal are the decisions done by the current patterns, and what's the rough percentage of usual code we see in the real world, for which the current patterns do not work well? What I am trying to gauge is if it is so broken that it should not exist (in other words, you regret sending the patch to the list before doing these updates), or is "already serviceable, but not perfect yet". Waiting for perfection takes forever. If the latter, letting the general public to use it to gather feedbacks by waiting for the dust to settle before making such updates is often better.
