On Thu, Mar 07, 2002 at 10:03:43AM -0500, Drew Northup wrote: > There is a reason that we didn't use the ones in the kernel. It is that > we need to have portability to other platforms. (There are other issues > too...., but for the moment, that is the most important.) This is not > to say that I am unhappy to see somebody working on something--but this > just isn't a patch that the main tree can use (or that, for GPL vs. LGPL > reasons, can really be included at all). > > Also, while we are on the subject, util-nexus.c is, if I remember > correctly, no just part of the linux kernel module, but it is part of > all kernel modules. Please check for things like this before submitting > a platform specific (if you know it to be such) patch. Also, please > check the mailinglist, as somebody may have discussed patching that code > before (and may be in the process of doing it...), or we may have > decided not to do that seemingly obvious thing that you are about to > patch to for some not so obvious reason.
Isn't it possible to use glibc's string functions? Those are pretty well optimized and glibc is LGPL'd. It's possible to add an autoconf check for systems which don't provide the functions and provide our own versions or just copy the glibc functions to plex86. I think the reason is obvious: speed. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: jeroen@openprojects
