[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: strsuftoi(3), strsuftou(3) proposal in libc
Worst example I remember was when someone standardised a getline(3)
function. The lack of forethought shown by some some software developers
over the years was amazing - an obvious thing to get standardised, even
decades later. This is why I will not name any C functions I write
just in case.
On another note, I do not want to have to distribute libnbcompat with any
code I write. I also find requiring it to be present, just to compile stuff
that I write, to be too onerous.
Not in libc, please.
On 1 November 2015 at 17:49, Mouse <mouse%rodents-montreal.org@localhost> wrote:
> > It's already done - libnbcompat in pkgsrc. Just write your program
> > with NetBSD libc API and use libnbcompat for whatever POSIX-like
> > platform. This is how I'm doing it - no big magic.
> Speaking as a code author, the headaches of that approach occur when
> some well-meaning soul adds yet another function to libc - and it
> happens to collide with a function in your program, a function that
> used to be in user namespace. I've got a program in which I had to
> rename heapsort to heap_sort, I think it was, because of that.
> /~\ The ASCII Mouse
> \ / Ribbon Campaign
> X Against HTML mouse%rodents-montreal.org@localhost
> / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Main Index |
Thread Index |