Re: Best practive for dependency incjection

2013-05-06 Thread Elmar Hinz
On Mon, May 6, 2013 at 11:27 AM, Pavel Sanda wrote: > Elmar Hinz wrote: > > The important point is, that testing leads to restructure the source > step by > > step in the spirit of more independency of each class. > > That "restructure" is probably what I called plans if I understand your > aim..

Re: Best practive for dependency incjection

2013-05-06 Thread Pavel Sanda
Elmar Hinz wrote: > The important point is, that testing leads to restructure the source step by > step in the spirit of more independency of each class. That "restructure" is probably what I called plans if I understand your aim... P

Re: Best practive for dependency incjection

2013-05-06 Thread Elmar Hinz
Hello Pavel. IIRC there were few discussions but no one ever came with realistic plan. > I don't think it needs a big plan at all. Each test is independed, so you can even mix tests from different frameworks. Also testing has already been started. Simply proceed instead of big plans. Especiall

Re: Best practive for dependency incjection

2013-05-05 Thread Pavel Sanda
Elmar Hinz wrote: > However with C++ it is necessary to mangage the memory usage. For dependency > injection this brings up the question, when and where to free the memory. > > Do you have a policy how to deal with this for Lyx in special and is there a > good tutorial how to handle that with C++