Messages in this thread | | | Date | Wed, 30 Jul 1997 11:04:53 -0600 (MDT) | From | Teunis Peters <> | Subject | glibc 2, Linux 2.x and the world of many patches! |
| |
Before anyone screams too loudly about my dislike/distrust of glibc I just want to point out one thing:
I'm slowly being convinced of the error of my ways <g>.
This move may take a while (it already has) but the light at the end of the tunnel may be worth the wait.
Developer-types (hi, all) should prolly be looking at updating code so it'll compile under the new glibc... the wins [for the most part] outway any lossage (and glibc will eventually get fast string funcs, yes? :)
Though adoption will have to be MUCH higher before any of the linux-distribs actively go with glibc... and this will hurt glibc in the short run.
Query : Why can't glibc have an asm/tree just like linux for system-specific inline optimizations? [it's not like this is hard to do or anything and the specific functions needed are MOST portable and stable :]
It'd be nice if glibc could do pentium-memcpy :)
Umm - I know of no other lists than linux-kernel so I'm kinda, uh, posting here... Is there a way of finding out others? (I have no usenet <sigh>)
Good day all! - Teunis
| |