[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: font-lock-syntactic-keywords obsolet?

From: Dmitry Gutov
Subject: Re: font-lock-syntactic-keywords obsolet?
Date: Wed, 29 Jun 2016 03:30:27 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Thunderbird/47.0

On 06/23/2016 07:30 PM, Alan Mackenzie wrote:

1)...  There were two functions in cc-fonts.el that were using
(point-max) as a limit for something, when they should have been using,
respectively, (min limit (point-max)), and limit.  A bit of playing
around suggests there is more to fix, there.

So now the raw strings are properly using limits? Does that mean there is a limit on the length of a raw string that CC Mode supports? (Testing indicates so).

Maybe it's not too terrible, but, depending on the limit's value, it could be a problem in certain specialized files (e.g. in a game sources where the author decided to keep some art assets in the code, or in some test files).

Anyway, that's the performance-vs-correctness tradeoff I've mentioned earlier. Using syntax-propertize-function, I've never seen the necessity to make that choice, so far. And Ruby has several counterparts to C++'s raw strings, all with irregular syntax.

2) ... This was caused by a low level function failing to do
(save-match-data ...) around a (looking-at ....) with the result that
the match-data was corrupted for the higher level function.  That bug's
been there for some while.

That works now, thanks.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]