> > Given the complexities of the code, I simply do not understand how anyone > can be confident that proposed changes would work *exactly* as before. > After 15 hours of intense study, I don't understand the code well enough to > have any confidence in *any* real changes to the code. > > If you, a rather clever, smart, experienced developer and also the author of this code, after 15 hours of intense study do not fully understand the code, shouldn't that tell you something about the quality of the code? If you cant fully understand the code, what chances to understand it will have the rest of us.
Now what I really don't understand is your decision not to fix this code even after you yourself had learned that it is far from being readable and maintainable code. Why don't you make it simple and readable? I could help if you need any help. I don't understand the code well enough to have any confidence in any real > changes to the code. > That is precisely why the real changes are necessary. I would say I don't have any confidence that it works correctly at all in its current state. That should be well enough reason to refactor this code, no matter how much time and effort will it take. But I guess, you'll prefer to leave this code as it is. I am tempted to put aside all my current tasks and write my own launchLeo.py which will monkey patch completely cofiguration code and just read settings from the database table. I guess it would greatly reduce number of code lines that has to be executed every time Leo opens new commander. Vitalije -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/63b72858-3f7d-4916-ac67-aeb6d2bebba9%40googlegroups.com.
