Hi Göran,

goran.krampe at bluefish.se wrote:

> ...

> And I can at this time, for anyone still reading, mention that I
> yesterday executed two unit tests green that made the very first partial
> dependency analysis. New class called SMDependencyEngine.

This is nice for you. And for me, too, if deps are finally coming into SM.

But this is also discouraging for my own coding: last night I've started
with classes
  DepSVersion, DepSTransformation, DepSPerformer,
but now I think it makes no sense to continue.

My idea has been to just make a backend with a clearly separated
interface to be used by SM and other tools, with the main target SM.

But if you have started to make your own thing, why should I continue?
To compete with a part of software from you, where you decide to use
yours or mine? I know, which I would use in such a situation...

Don't understand me wrong: I can understand that you've just started
without making yourself dependent from others.


Possibly I've misinterpreted your call for help in this area.


Greetings
Stephan

> ...
-- 
Stephan Rudlof (sr at evolgo.de)
   "Genius doesn't work on an assembly line basis.
    You can't simply say, 'Today I will be brilliant.'"
    -- Kirk, "The Ultimate Computer", stardate 4731.3