File: al_fungetc.3

package info (click to toggle)
allegro5 2%3A5.0.10-3
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 14,856 kB
  • ctags: 15,948
  • sloc: ansic: 87,540; cpp: 9,693; objc: 3,491; python: 2,057; sh: 829; makefile: 93; perl: 37; pascal: 24
file content (31 lines) | stat: -rw-r--r-- 874 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
.TH al_fungetc 3 "" "Allegro reference manual"
.SH NAME
.PP
al_fungetc \- Allegro 5 API
.SH SYNOPSIS
.IP
.nf
\f[C]
#include\ <allegro5/allegro.h>

int\ al_fungetc(ALLEGRO_FILE\ *f,\ int\ c)
\f[]
.fi
.SH DESCRIPTION
.PP
Ungets a single byte from a file.
Pushed\-back bytes are not written to the file, only made available for
subsequent reads, in reverse order.
.PP
The number of pushbacks depends on the backend.
The standard I/O backend only guarantees a single pushback; this depends
on the libc implementation.
.PP
For backends that follow the standard behavior, the pushback buffer will
be cleared after any seeking or writing; also calls to al_fseek(3) and
al_ftell(3) are relative to the number of pushbacks.
If a pushback causes the position to become negative, the behavior of
al_fseek(3) and al_ftell(3) are undefined.
.SH SEE ALSO
.PP
al_fgetc(3), al_get_errno(3)