Re: [Fenfire-dev] Summary regarding single branch

[Benja Fallenstein]

Hi!

Matti Katila wrote:
> On Sat, 17 Jul 2004, Benjamin-Elias Fallenstein wrote:
> > > def write(graph):   to   def write(graph, outputstream=None): 
> >
> > That's exactly how I want to do it. The point was that when the writer is 
> > in Fenfire, and the added feature is needed in Loom, then both Loom and 
> > Fenfire need to be changed to do it the way you say.
>
> No. That change doesn't break anything because the function is overloaded.
> Everything old still works.

I said that both Loom and Fenfire need to be changed.

Fenfire needs to be changed if the change is to be in writer.py. Loom 
needs to be changed if it is to make use of the new feature.

> > I want to do it the way you say, and therefore, I want to be allowed to 
> > change both projects at the same time :-) 
>
> Yes I understand that you want to change but I think you need first to 
> make the change in fenfire and then in ex-loom because of ex-loom 
> depends of fenfire. 

?

Why can't it be made in both projects at the same time?

> The change in loom is binded with the change in fenfire but not atomic in 
> sense that there are also three other programs that use the same writer.

'Atomic' means that both changes happen in one commit. I don't 
understand what you mean by 'three other programs that use the same 
writer' and what it has to do with whether the change is atomic? =)

Cheers,
- Benja