Re: [PATCH 15/15] kconf: Check for eof from input stream.

Hi,

On Thu, 19 Jan 2006, Bodo Eggert wrote:

> > That would be ^C. ^D means end-of-file and it's up to the application, 
> > whether it needs further information to continue or not.
> 
> If it does need data, it SHOULD NOT invent it, especially if inventing
> this data has no benefit and causes unexpected beahviour and random 
> breakage.

It doesn't "invent" anything, so I don't see your point.

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [PATCH 15/15] kconf: Check for eof from input stream.
    • From: Bodo Eggert <[email protected]>
  • Re: [PATCH 15/15] kconf: Check for eof from input stream.
    • From: Roman Zippel <[email protected]>
  • Re: [PATCH 15/15] kconf: Check for eof from input stream.
    • From: Bodo Eggert <[email protected]>

• Prev by Date: Re: [PATCH 15/15] kconf: Check for eof from input stream.
• Next by Date: Re: [PATCH] 2.6.16-rc1-mm1 - produce useful info for kzalloc with DEBUG_SLAB
• Previous by thread: Re: [PATCH 15/15] kconf: Check for eof from input stream.
• Next by thread: [PATCH 13/15] irda/nsc-ircc: Add ISAPNP support
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]