close.c.3

Can for Linux的源代码！

.TH "close.c" 3 "2 Jun 2006" "can4linux" \" -*- nroff -*-
.ad l
.nh
.SH NAME
close.c \- 
.SH SYNOPSIS
.br
.PP
.SS "Functions"

.in +1c
.ti -1c
.RI "__LDDK_CLOSE_TYPE \fBcan_close\fP (__LDDK_CLOSE_PARAM)"
.br
.RI "\fIint close(int fd); close a file descriptor \fP"
.in -1c
.SS "Variables"

.in +1c
.ti -1c
.RI "int \fBCan_isopen\fP []"
.br
.in -1c
.SH "Detailed Description"
.PP 
\fBAuthor:\fP
.RS 4
Heinz-J黵gen Oertel, port GmbH 
.PP
\fBRevision\fP.RS 4
1.1 
.RE
.PP
\fBDate\fP.RS 4
2006/04/21 16:25:53 
.RE
.PP
.RE
.PP

.SH "Function Documentation"
.PP 
.SS "__LDDK_CLOSE_TYPE can_close (__LDDK_CLOSE_PARAM)"
.PP
int close(int fd); close a file descriptor 
.PP
\fBParameters:\fP
.RS 4
\fIfd\fP The descriptor to close.
.RE
.PP
\fBclose\fP closes a file descriptor, so that it no longer refers to any device and may be reused. 
.PP
\fBReturns:\fP
.RS 4
close returns zero on success, or -1 if an error occurred. 
.RE
.PP
\fBERRORS\fP.RS 4

.RE
.PP
the following errors can occur
.PP
.PD 0
.IP "\(bu" 2
\fCBADF\fP \fBfd\fP isn't a valid open file descriptor 
.PP

.SH "Author"
.PP 
Generated automatically by Doxygen for can4linux from the source code.