linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Glynn Clements <glynn.clements@virgin.net>
To: Daniel <uval@rz.uni-karlsruhe.de>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Check serial port buffer
Date: Fri, 10 May 2002 11:07:08 +0100	[thread overview]
Message-ID: <15579.39884.432208.375087@cerise.nosuchdomain.co.uk> (raw)
In-Reply-To: <002a01c1f802$21939e30$544615ac@stud.unikarlsruhe.de>


Daniel wrote:

> > Can anyoune tell me how can I check the first byte of the serial port
> > buffer without removing it from the buffer?
> 
> doesn't ungetch() work ?

ungetc() puts the character back in the stdio buffer. It can't put it
back into the underlying OS stream.

-- 
Glynn Clements <glynn.clements@virgin.net>

      reply	other threads:[~2002-05-10 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 12:20 Check serial port buffer Iorga Alin
2002-05-10  9:07 ` Daniel
2002-05-10 10:07   ` Glynn Clements [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15579.39884.432208.375087@cerise.nosuchdomain.co.uk \
    --to=glynn.clements@virgin.net \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=uval@rz.uni-karlsruhe.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).