perlman gods <HR> <H1><A NAME="NAME">NAME</A></H1> perlapio - perl's IO abstraction interface. <HR> <H1><A NAME="SYNOPSIS">SYNOPSIS</A></H1> <PRE> PerlIO *PerlIO_stdin(void); PerlIO *PerlIO_stdout(void); PerlIO *PerlIO_stderr(void); </PRE> <PRE> PerlIO *PerlIO_open(const char *,const char *); int PerlIO_close(PerlIO *); </PRE> <PRE> int PerlIO_stdoutf(const char *,...) int PerlIO_puts(PerlIO *,const char *); int PerlIO_putc(PerlIO *,int); int PerlIO_write(PerlIO *,const void *,size_t); int PerlIO_printf(PerlIO *, const char *,...); int PerlIO_vprintf(PerlIO *, const char *, va_list); int PerlIO_flush(PerlIO *); </PRE> <PRE> int PerlIO_eof(PerlIO *); int PerlIO_error(PerlIO *); void PerlIO_clearerr(PerlIO *); </PRE> <PRE> int PerlIO_getc(PerlIO *); int PerlIO_ungetc(PerlIO *,int); int PerlIO_read(PerlIO *,void *,size_t); </PRE> <PRE> int PerlIO_fileno(PerlIO *); PerlIO *PerlIO_fdopen(int, const char *); PerlIO *PerlIO_importFILE(FILE *, int flags); FILE *PerlIO_exportFILE(PerlIO *, int flags); FILE *PerlIO_findFILE(PerlIO *); void PerlIO_releaseFILE(PerlIO *,FILE *); </PRE> <PRE> void PerlIO_setlinebuf(PerlIO *); </PRE> <PRE> long PerlIO_tell(PerlIO *); int PerlIO_seek(PerlIO *,off_t,int); int PerlIO_getpos(PerlIO *,Fpos_t *) int PerlIO_setpos(PerlIO *,Fpos_t *) void PerlIO_rewind(PerlIO *); </PRE> <PRE> int PerlIO_has_base(PerlIO *); int PerlIO_has_cntptr(PerlIO *); int PerlIO_fast_gets(PerlIO *); int PerlIO_canset_cnt(PerlIO *); </PRE> <PRE> char *PerlIO_get_ptr(PerlIO *); int PerlIO_get_cnt(PerlIO *); void PerlIO_set_cnt(PerlIO *,int); void PerlIO_set_ptrcnt(PerlIO *,char *,int); char *PerlIO_get_base(PerlIO *); int PerlIO_get_bufsiz(PerlIO *); </PRE> <HR> <H1><A NAME="DESCRIPTION">DESCRIPTION</A></H1> Perl's source code should use the above functions instead of those defined in ANSI C's stdio.h. The perl headers will <CODE>#define</CODE> them to the I/O mechanism selected at Configure time. The functions are modeled on those in stdio.h, but parameter order has been ``tidied up a little''. <DL> <DT><A NAME="item_PerlIO">PerlIO *</A> <DD> This takes the place of FILE *. Like FILE * it should be treated as opaque (it is probably safe to assume it is a pointer to something). <DT><A NAME="item_PerlIO_stdin">PerlIO_stdin(), PerlIO_stdout(), PerlIO_stderr()</A> <DD> Use these rather than <CODE>stdin</CODE>, <CODE>stdout</CODE>, <CODE>stderr</CODE>. They are written to look like ``function calls'' rather than variables because this makes it easier to make them function calls if platform cannot export data to loaded modules, or if (say) different ``threads'' might have different values. <DT><A NAME="item_PerlIO_open">PerlIO_open(path, mode), PerlIO_fdopen(fd,mode)</A> <DD> These correspond to <CODE>fopen()/fdopen()</CODE> arguments are the same. <DT><A NAME="item_PerlIO_printf">PerlIO_printf(f,fmt,...), PerlIO_vprintf(f,fmt,a)</A> <DD> These are <CODE>fprintf()/vfprintf()</CODE> equivalents. <DT><A NAME="item_PerlIO_stdoutf">PerlIO_stdoutf(fmt,...)</A> <DD> This is <CODE>printf()</CODE> equivalent. printf is #defined to this function, so it is (currently) legal to use [perlfunc:printf|printf(fmt,...)] in perl sources. <DT><A NAME="item_PerlIO_read">PerlIO_read(f,buf,count), PerlIO_write(f,buf,count)</A> <DD> These correspond to <CODE>fread()</CODE> and <CODE>fwrite().</CODE> Note that arguments are different, there is only one ``count'' and order has ``file'' first. <DT><A NAME="item_PerlIO_close">PerlIO_close(f)</A><DD> <DT><A NAME="item_PerlIO_puts">PerlIO_puts(f,s), PerlIO_putc(f,c)</A> <DD> These correspond to <CODE>fputs()</CODE> and <CODE>fputc().</CODE> Note that arguments have been revised to have ``file'' first. <DT><A NAME="item_PerlIO_ungetc">PerlIO_ungetc(f,c)</A> <DD> This corresponds to <CODE>ungetc().</CODE> Note that arguments have been revised to have ``file'' first. <DT><A NAME="item_PerlIO_getc">PerlIO_getc(f)</A> <DD> This corresponds to <CODE>getc().</CODE> <DT><A NAME="item_PerlIO_eof">PerlIO_eof(f)</A> <DD> This corresponds to <CODE>feof().</CODE> <DT><A NAME="item_PerlIO_error">PerlIO_error(f)</A> <DD> This corresponds to <CODE>ferror().</CODE> <DT><A NAME="item_PerlIO_fileno">PerlIO_fileno(f)</A> <DD> This corresponds to <CODE>fileno(),</CODE> note that on some platforms, the meaning of ``fileno'' may not match Unix. <DT><A NAME="item_PerlIO_clearerr">PerlIO_clearerr(f)</A> <DD> This corresponds to <CODE>clearerr(),</CODE> i.e., clears 'eof' and 'error' flags for the ``stream''. <DT><A NAME="item_PerlIO_flush">PerlIO_flush(f)</A> <DD> This corresponds to <CODE>fflush().</CODE> <DT><A NAME="item_PerlIO_tell">PerlIO_tell(f)</A> <DD> This corresponds to <CODE>ftell().</CODE> <DT><A NAME="item_PerlIO_seek">PerlIO_seek(f,o,w)</A> <DD> This corresponds to <CODE>fseek().</CODE> <DT><A NAME="item_PerlIO_getpos">PerlIO_getpos(f,p), PerlIO_setpos(f,p)</A> <DD> These correspond to <CODE>fgetpos()</CODE> and <CODE>fsetpos().</CODE> If platform does not have the stdio calls then they are implemented in terms of <CODE>PerlIO_tell()</CODE> and <CODE>PerlIO_seek().</CODE> <DT><A NAME="item_PerlIO_rewind">PerlIO_rewind(f)</A> <DD> This corresponds to <CODE>rewind().</CODE> Note may be redefined in terms of <CODE>PerlIO_seek()</CODE> at some point. <DT><A NAME="item_PerlIO_tmpfile">PerlIO_tmpfile()</A> <DD> This corresponds to <CODE>tmpfile(),</CODE> i.e., returns an anonymous PerlIO which will automatically be deleted when closed. </DL> <HR> <H2><A NAME="Co_existence_with_stdio">Co-existence with stdio</A></H2> There is outline support for co-existence of PerlIO with stdio. Obviously if PerlIO is implemented in terms of stdio there is no problem. However if perlio is implemented on top of (say) sfio then mechanisms must exist to create a FILE * which can be passed to library code which is going to use stdio calls. <DL> <DT><A NAME="item_PerlIO_importFILE">PerlIO_importFILE(f,flags)</A> <DD> Used to get a PerlIO * from a FILE *. May need additional arguments, interface under review. <DT><A NAME="item_PerlIO_exportFILE">PerlIO_exportFILE(f,flags)</A> <DD> Given an PerlIO * return a 'native' FILE * suitable for passing to code expecting to be compiled and linked with ANSI C stdio.h. The fact that such a FILE * has been 'exported' is recorded, and may affect future PerlIO operations on the original PerlIO *. <DT><A NAME="item_PerlIO_findFILE">PerlIO_findFILE(f)</A> <DD> Returns previously 'exported' FILE * (if any). Place holder until interface is fully defined. <DT><A NAME="item_PerlIO_releaseFILE">PerlIO_releaseFILE(p,f)</A> <DD> Calling PerlIO_releaseFILE informs PerlIO that all use of FILE * is complete. It is removed from list of 'exported' FILE *s, and associated PerlIO * should revert to original behaviour. <DT><A NAME="item_PerlIO_setlinebuf">PerlIO_setlinebuf(f)</A> <DD> This corresponds to <CODE>setlinebuf().</CODE> Use is deprecated pending further discussion. (Perl core uses it only when ``dumping''; it has nothing to do with $| auto-flush.) </DL> In addition to user API above there is an ``implementation'' interface which allows perl to get at internals of PerlIO. The following calls correspond to the various FILE_xxx macros determined by Configure. This section is really of interest to only those concerned with detailed perl-core behaviour or implementing a PerlIO mapping. <DL> <DT><A NAME="item_PerlIO_has_cntptr">PerlIO_has_cntptr(f)</A> <DD> Implementation can return pointer to current position in the ``buffer'' and a count of bytes available in the buffer. <DT><A NAME="item_PerlIO_get_ptr">PerlIO_get_ptr(f)</A> <DD> Return pointer to next readable byte in buffer. <DT><A NAME="item_PerlIO_get_cnt">PerlIO_get_cnt(f)</A> <DD> Return count of readable bytes in the buffer. <DT><A NAME="item_PerlIO_canset_cnt">PerlIO_canset_cnt(f)</A> <DD> Implementation can adjust its idea of number of bytes in the buffer. <DT><A NAME="item_PerlIO_fast_gets">PerlIO_fast_gets(f)</A> <DD> Implementation has all the interfaces required to allow perl's fast code to handle <FILE> mechanism. <PRE> PerlIO_fast_gets(f) = PerlIO_has_cntptr(f) && \ PerlIO_canset_cnt(f) && \ `Can set pointer into buffer' </PRE> <DT><A NAME="item_PerlIO_set_ptrcnt">PerlIO_set_ptrcnt(f,p,c)</A> <DD> Set pointer into buffer, and a count of bytes still in the buffer. Should be used only to set pointer to within range implied by previous calls to <CODE>PerlIO_get_ptr</CODE> and <CODE>PerlIO_get_cnt</CODE>. <DT><A NAME="item_PerlIO_set_cnt">PerlIO_set_cnt(f,c)</A> <DD> Obscure - set count of bytes in the buffer. Deprecated. Currently used in only doio.c to force count < -1 to -1. Perhaps should be PerlIO_set_empty or similar. This call may actually do nothing if ``count'' is deduced from pointer and a ``limit''. <DT><A NAME="item_PerlIO_has_base">PerlIO_has_base(f)</A> <DD> Implementation has a buffer, and can return pointer to whole buffer and its size. Used by perl for -T / -B tests. Other uses would be very obscure... <DT><A NAME="item_PerlIO_get_base">PerlIO_get_base(f)</A> <DD> Return start of buffer. <DT><A NAME="item_PerlIO_get_bufsiz">PerlIO_get_bufsiz(f)</A> <DD> Return total size of buffer. </DL> <HR> Return to the [Library]