On Thu, Jan 17, 2013 at 10:41 AM, Pascal Obry <[email protected]> wrote: > > Johannes, > >> from a design standpoints, it's just a nice thing to have code cleanly >> separated (you don't like cropping? delete one file!). so even though >> we could from a practical view just statically compile in all our >> modules, we don't, because it's a nice modular separation of the mess >> we usually create while coding. > > Oh I see, that's not at the code level but at the runtime one the > problem. You want the iop share lib to be fully independent of the core > application. > >> yes, but the way to make sure this happens is to at least include a >> check if the versions line up (and not crash in case someone forgot to >> clean up all relevant places). >> >> which brings be back to my original point. how do you now >> know/remember all the places that are affected by a parameter change >> in the module. not quite as simple as `all in this file only' anymore. >> >> i guess as you're in darkroom mode doing this (right?), you could just > > Right. > >> find the module and check module->version() for the hardcoded version >> your current code supports. that way at least it would rot gracefully >> :) > > Ok, will do that. > > At least I had something right, I was really missing some important > information... New in dt :( Sorry for the mess!
no worries, we really appreciate your efforts to streamline dt :) -jo ------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
