Simon Josefsson <[EMAIL PROTECTED]> writes: > 1) Port the libc LGPL getdelim into a gnulib module. > 2a) Port the libc LGPL getline into a gnulib module. > 2b) Write a gnulib LGPL getline module that use the gnulib LGPL getdelim. > 3) Keep the current getndelim2 as a GPL module. > > The libc getline seem somewhat different from libc getdelim; > presumably it is faster than a simple getline implementation that use > getdelim. I'm not sure this matter for gnulib though, so I prefer 2b > for simplicity.
2b might be simpler in the short run, but will it be in the long run? Or are you assuming that libc getline won't ever change much? > Finally, I'm not sure we can ever hope to sync these files between > gnulib and libc. The libc implementation look inside the FILE > structure. Gnulib code can't do that. It could do so conditionally. For example, it might use the stdio_ext.h interface on Solaris. <http://docs.sun.com/app/docs/doc/816-5168/6mbb3hr5j?q=stdio_ext&a=view>. However, you're the expert here, and if you've judged that 2b) is less work overall, perhaps we should just do that. We can always switch to 2a) later if need be. _______________________________________________ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib
