support CMAKE_<LANG>_... variables

#197 , solve the LANG issue first,

the PROJECT is harder, will solve it later after this pull request.
the cache will be invalid if user switch to another project, I assume user
will have a rest for ten minutes before switching project.

On Fri, Oct 31, 2014 at 4:03 PM, chen bin <chenbin.sh@gmail.com> wrote:

> nothing expensive at this stage, but in next pull request, I need replace
> PROJECT_source_dir, that's really expensive. the algorithm is like search
> to the root directory, then scan recursively to find the CMakeLists.txt,
> use regex to grep the project name (I was told by at least one cmake user
> he use variable in project name), so some recursive algorithm to fetch the
> project name is need.
>
> I think recursive search the directory and grep each CMakeLists.txt could
> be expensive.
>
> On Fri, Oct 31, 2014 at 12:17 PM, Dmitry Gutov <notifications@github.com>
> wrote:
>
>> In company-cmake.el:
>>
>> >    "Regexp to match the candidates.")
>> >
>> >  (defvar company-cmake-modes '(cmake-mode)
>> >    "Major modes in which cmake may complete.")
>> >
>> > +(defvar company-cmake-candidates-cache nil
>>
>> Could you explain the need for using the cache? What operations are
>> particularly expensive?
>>
>> Why invalidate it in 10 minutes? What part of it can become stale? Can't
>> we invalidate it on some specific value?
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/company-mode/company-mode/pull/214/files#r19647188>.
>>
>
>
>
> --
> help me, help you.
>



-- 
help me, help you.