Package: libc0.2 Version: 2.1.2-0pre12 Severity: normal Hello,
libc on hurd behaves as per documentation in that only one push-back by ungetc is provided (two or more in succession have no effect). So why am I calling this a bug?! This is contrary to the behaviour of libc under linux which can cause some packages to stop working. In particular, any package that does a look-ahead on a "unicode" text-file would need to get one wide character or two bytes and push them back into the stream. One such program is "omega" which is the unicode version of TeX. While such programs could use "fseek" and "ftell", Roland points out that this could cause problems with pipes and other non-file streams. I also ran some checks on linux and found that the ungetc there (which is part of libc/libio) can make upwards of 2048 ungetc's---even when there has been no read from the stream! Without going into the desirability of this "feature" couldn't we have atleast 8 ungetc's (64-bit) under the hurd? Thanks and regards, Kapil. -- System Information Debian Release: potato Kernel Version: GNU hurd 0.2 GNUmach-1.2/Hurd-0.2 i386-AT386 unknown
