home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.perl
- Path: sparky!uunet!spsgate!mogate!newsgate!chdasic.sps.mot.com!dichter
- From: dichter@chdasic.sps.mot.com (Carl Dichter)
- Subject: Re: Prompting for input
- Message-ID: <1992Sep9.175931.18694@newsgate.sps.mot.com>
- Sender: usenet@newsgate.sps.mot.com
- Nntp-Posting-Host: 223.197.55.10
- Organization: SPS
- References: <memo.616870@cix.compulink.co.uk>
- Date: Wed, 9 Sep 1992 17:59:31 GMT
- Lines: 26
-
- In article <memo.616870@cix.compulink.co.uk>, pmoore@cix.compulink.co.uk (Paul Moore) writes:
- |>
- |> In his posting, James Gillespie says:
- |> > pause. It appears to me that there must be something left
- |> > on STDIN as a result of entering the string "n\n", but I
- |> > can't find anything in the Camel book about such an
- |> > occurrence, or how to "suck"
- |>
- |> Er - what about the "\n"? getc only gets a single character.
- |>
- |> Gustav.
- |>
- |> ------------------------------------------------------------------------
- |> Paul Moore (pmoore@cix.compulink.co.uk) |
- |> ------------------------------------------------------------------------
- |> Programming is the process of debugging an empty source file
- |> ------------------------------------------------------------------------
- |>
-
- That's why Tom says to use <STDIN>.
- That way it "eats" the newline too.
-
- ----------------------
- Carl R. Dichter "iwannanugui"
- Motorola ASIC Division
- email: dichter@chdasic.sps.mot.com
-