[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Fenfire-dev] Summary regarding single branch

From: Benjamin-Elias Fallenstein
Subject: Re: [Fenfire-dev] Summary regarding single branch
Date: Sat, 17 Jul 2004 15:52:53 +0200 (MEST)

> On Fri, 16 Jul 2004, Benja Fallenstein wrote: 
> > example, copying+pasting an RDF writer from Fenfire into Loom because 
> > need to add a feature to it, modify it there, and then after some time  
> > put it back to Fenfire, if it doesn't get forgotten in Loom. It's 
> > work to make our code somewhat better without artificial constraints  
> > like that. 
> My programming teacher always said that when you copy+paste you are 
> something wrong. I didn't understand why couldn't you add a new feature  
> without copy+paste? For example I added a simple new feature to that RDF  
> writer. The change was like this: 
> def write(graph):   to   def write(graph, outputstream=None): 
> to use storm's pool.getBlockOutputStream() with writer. Feature added,  
> though not yet commited, could you do changes like this? 
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. I want to do it the 
way you say, and therefore, I want to be allowed to change both projects 
at the same time :-) 
- Benja 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]