Re: [CEDET-devel] Unsolved includes using ede-cpp-root-project definition

[Lluís <xs...@gm...>]

Eric M Ludlam writes:

> On 05/07/2013 04:19 PM, Lluís wrote:
>> Pamela Carreño writes:
>> 
>>> Hi,
>>> I'm using ede-cpp-root-project to create an ede-project from existing files.
>> 
>>> (ede-cpp-root-project "FLANN"
>>> :name "Flann1.8"
>>> :file "~/Documents/PhD/Code/Kd-Trees_NNS/Flann/CMakeLists.txt"
>> 
>> I think EDE does not expand filenames for you (maybe that should be implemented,
>> or at least clearly documented). Try this instead:
>> 
>> :file (expand-file-name "~/Documents/PhD/Code/Kd-Trees_NNS/Flann/CMakeLists.txt")
>> 

> I checked, and I'm pretty sure the :file is expanded.  For example, see 
> this from ede/cpp-root.el:

>    (let ((f (expand-file-name (oref this :file))))
> ...
>      (oset this :file f)

> Is there something else causing problems?

I just re-checked, and using "~" in my ":file" does not "activate" the project
when I edit a file from it (although it does not complain about a non-existing
":file").


>> BTW, this reminds me that all my 'ede-cpp-root-project' are guarded with a
>> 'file-exists-p', as EDE otherwise throws out an error complaining about
>> non-existing files.
>> 
>> Is there a reason for this behaviour? Wouldn't it be more comfortable to check
>> that inside EDE?

> What do you propose EDE do if the incoming file doesn't exist?  Wouldn't 
> it still throw an error, or do you think it needs a better error?

I think that attribute ":file" should act as a "guard" to know whether and when
to associate a project to another file. Thus creating an "ede-cpp-root-project"
with a non-existing ":file" should not complain (but the project should exist in
EDE, just in case the file is created later).


Lluis

-- 
 "And it's much the same thing with knowledge, for whenever you learn
 something new, the whole world becomes that much richer."
 -- The Princess of Pure Reason, as told by Norton Juster in The Phantom
 Tollbooth