jgdavid...@mac.com wrote: > > Hi, > > Every few years we talk about what's next for the strategic direction > of AOLserver which is great. In addition to the ideas below (which > are cool), I always bring up this question: Should we dump the > Windows port in favor of a clean Unix code base, configure, build, > and install? > > I wrote most of that weird Windows code, including the goofy nsconfig > stuff. Some of it was curious, maybe even clever, but in the end it > was a distraction. It's impact on the config/build process in > particular was pretty significant. Today's Linux and OS/X > environments are so much more amenable to Aolserver, with threaded > Tcl ready to go, gcc/make all pretty stable. It wasn't like that in > the early days! For me, a purge of the Windows code and then an > aggressive scan for anything still not 64-bit compatible and cleanly > build-able using standard configure/gcc/gmake tools would be quite > refreshing :)
Even more radically, could we drop autoconf entirely in favor of 2 or 3 clean makefiles? The general feeling I've gotten is that modern unix platforms are far less different now than several years ago. -J ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
