> *much* rather wait 90 seconds for each build that try to maintain a giant > tabulation with thousands of entries, which go out of date every time a new > patch or revision of libc or the compiler or the os or the linker comes along.
there seems to be an affliction in the unix world, that started out as (a) you are required to use the esoteric features of a library within milliseconds of the release of a new version, and (b) libraries must have the maximum amount of api churn possible recently this has morphed into libraries removing "old" working functions on dot releases because of the the first condition. "modern" languages like perl and python even subscribe to this model. it's okay to break the language between releases. - erik
