Thomas Lussnig <[EMAIL PROTECTED]> writes: > your page is not realy very usefull. First yes it describe how to code > protocol independent but > the big problem is it is ONLY valid for platforms with are full > compatible with the newest functions. > In the first change of wget i also had reduced the functions to these > minimal set. But the problem > is that you can not relay that all platforms where wget work support > the sugested way. So there > is still the need to use many different methods with ifdef's. > 2. if is also important that the adress resolutions isfast cached and > not always resolved again. > 3. There are some point in the protocols of HTTP and FTP where the > different format of readable adress are used > and on ftp even different command set's.
These three points sum up pretty well why a protocol-independent coding style was not chosen for Wget. Besides, I don't think the CVS version is that hard to maintain, once you understand what's going on. The code is IMHO no harder to read than 1.9.1, and doesn't require mapped addresses to boot.
