|
From: | Dmitry Gutov |
Subject: | Re: {Spam?} Re: progmodes/project.el and search paths |
Date: | Fri, 7 Aug 2015 15:17:36 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Thunderbird/40.0 |
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".
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.
[Prev in Thread] | Current Thread | [Next in Thread] |