On 2013-05-25 13:56, Axel Simon wrote: > Uh, but code duplication means you have to fix bugs in two places.
Yes, it absolutely sucks. > So is there no way to build CPP'd code base once as gtk2 with one > cabal file and then to build it as gtk3 with another cabal file. Then > you'd have one code base and CPP stuff managing the difference between > them. > Isn't it a bit like the GHC_VERSION and GTK_VERSION macros? > Eventually you might want to get rid of everything that is inside > #ifdefs for versions that you don't want to support any longer (e.g. > in a few years you might get rid of everything that is Gtk2 related). I agree, this way is superior -- I just hadn't thought of it. Now that it's been suggested, I intend to roll back the current change and implement this ASAP. ~d ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Gtk2hs-devel mailing list Gtk2hs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk2hs-devel
