On Fri, Sep 04, 2009 at 10:37:58AM +0100, Roy Marples <[email protected]> wrote:
> Not at all unlike the glibc function getline(3) which was accepted by
> POSIX as is and didn't cause any undue grief to applications which
> already had a getline function? ;)
comparing a netbsd pseudostandard and posix is indeed a weird comparison
(you vastly overestimate the importance of netbsd vs. an extremely widely
implemented industry standard), but you missed the crucial difference:
getline is NOT visible in the standard header file until it is requested
to show up.
popcount is neither standardised, nor will it likely be standardised -
getline was going to be standardised for many years now.
and getline did not conflict with programs not asking for extensions
explicitly, which urxvt does not do on netbsd.
so yeah, the mindless netbsd breakage *is* *indeed* *totally* *unlike* the
getline example.
even if it were, the argument would boil down to "every bug any os
implements netbsd should implement too?". that's hardly convincing, but
maybe not so surprising giving you can't see the difference between
stomping into progam namespaces thus bluntly and better approaches. there
is no magic bullet, but you can always shoot yourself and hang yourself
too.
> Anyway, as long as it's fixed :)
so it's fixed and the workaround in urxvt is not needed anymore(?)
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
