[EMAIL PROTECTED] (Karl Berry) writes:
> > I guess the module rename would make it obvious to anyone using the old
> > 'malloc' module that they now need to choose which semantics they want,
> > the simpler 'malloc-gnu' or the POSIX-compliant 'malloc-posix'.
>
> Haven't we implicitly been assuming/providing malloc-gnu since day 1?
> Do we really need to force all gnulib users ('cause pretty much everyone
> needs malloc, after all) to educate themselves about the issue and make
> a choice? Can we just keep malloc as malloc-gnu?
I agree, but I don't have a strong opinion. I think the assumption and
default has been that gnulib implements replacement for normal GNU
system behavior. If an application only assumes POSIX behaviour, they
could chose 'malloc-posix' rather than 'malloc'.
/Simon
