On Wednesday 20 April 2005 05:55 am, Herold Heiko wrote: > (sorry for the late answer, three days of 16+ hours/day migration aren't > fun, UPS battery exploding inside the UPS almost in my face even less) > > > -----Original Message----- > > From: Hrvoje Niksic [mailto:[EMAIL PROTECTED] > > > > Herold Heiko <[EMAIL PROTECTED]> writes: > > > do have a compiler but aren't really developers (yet) (for example > > > first year CS students with old lab computer compilers). > > > > From my impressions of the Windows world, non-developers won't touch > > source code anyway -- they will simply use the binary. > > I feel I must dissent. Even today I'm not exactly a developer, I certainly > wasn't when I first placed my greedy hands on wget sources (in order to add > a couple of chars to URL_UNSAFE... back in 98 i think). I just knew where I > could use a compiler and followed instructions. > I'd just like wget still being compilable in an old setup by (growing) > newbies, for the learning value. Maybe something like a small note in the > windows/Readme instructions would be ok, as by the enclosed patch ?
publishing a separate patch on the website and including it in the tarball along with a note in windows/Readme is ok for me. but including an ugly workaround in the main sources just to support some older versions of microsoft c is definitely not. -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi University of Ferrara - Dept. of Eng. http://www.ing.unife.it Institute of Human & Machine Cognition http://www.ihmc.us Deep Space 6 - IPv6 for Linux http://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
