Re: {Spam?} Re: progmodes/project.el and search paths

[David Engster]

Dmitry Gutov writes:
> On 08/07/2015 02:43 PM, David Engster wrote:
>
>> Despite what may have been said, project.el is *not* meant to be some
>> kind of "base class" for different project systems (that was at least
>> what I initially thought, and which you seem to think as well). The way
>> I see it, project.el is more like an adapter, although one that
>> delegates the actual implementation, so something like an "abstract
>> adapter".
>
> In OOP terms, it most closely resembles an "interface".

EDE already has an interface. project.el allows to use (a small part of)
that interface through another, hence 'adapter'.

>> Dmitry and Stefan are saying that this adapter should only
>> provide the information that is common to all possible project systems,
>> which pretty much means "the list of files/directories that are part of
>> this project".
>
> Not necessarily. As has been touched on in a related discussion, it
> should be possible, for example, to define a fairly agnostic
> project-build-targets (or "tasks", not sure which is the more common
> term).
>
> I'm sure the list can be continued.

Yes, but your usual answer so far was that you want a concrete package
that needs it, so there's a chicken/egg problem here.

-David