.\" Generated by the Allegro makedoc utility
.TH PACKFILE_VTABLE 3alleg4 "version 4.4.3" "Allegro" "Allegro manual"
.SH NAME
PACKFILE_VTABLE \- Packfile vtable structure, for custom packfiles. Allegro game programming library.\&
.SH SYNOPSIS
.B #include <allegro.h>

.sp
.B typedef struct PACKFILE_VTABLE
.SH DESCRIPTION

.nf
   int pf_fclose(void *userdata);
   int pf_getc(void *userdata);
   int pf_ungetc(int c, void *userdata);
   long pf_fread(void *p, long n, void *userdata);
   int pf_putc(int c, void *userdata);
   long pf_fwrite(const void *p, long n, void *userdata);
   int pf_fseek(void *userdata, int offset);
   int pf_feof(void *userdata);
   int pf_ferror(void *userdata);
   
.fi
This is the vtable which must be provided for custom packfiles, which then
can read from and write to wherever you like (eg. files in memory). You
should provide all the entries of the vtable, even if they are empty stubs
doing nothing, to avoid Allegro (or you) calling a NULL method at some
point.

.SH SEE ALSO
.BR pack_fopen_vtable (3alleg4),
.BR expackf (3alleg4)