From: Gurusamy Sarathy Date: Sat, 17 Oct 1998 02:42:01 +0000 (+0000) Subject: clarify section name rules for typemaps X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=7e9d670dca4a9932a4ebf592c7fc054ce4d3bdc1;p=p5sagit%2Fp5-mst-13.2.git clarify section name rules for typemaps p4raw-id: //depot/perl@1995 --- diff --git a/pod/perlxs.pod b/pod/perlxs.pod index c578a2e..2e02247 100644 --- a/pod/perlxs.pod +++ b/pod/perlxs.pod @@ -1212,13 +1212,15 @@ getnetconfigent() XSUB and an object created by a normal Perl subroutine. The typemap is a collection of code fragments which are used by the B compiler to map C function parameters and values to Perl values. The typemap file may consist of three sections labeled C, C, and -C. The INPUT section tells the compiler how to translate Perl values +C. Any unlabelled initial section is assumed to be a C +section if a name is not explicitly specified. The INPUT section tells +the compiler how to translate Perl values into variables of certain C types. The OUTPUT section tells the compiler how to translate the values from certain C types into values Perl can understand. The TYPEMAP section tells the compiler which of the INPUT and OUTPUT code fragments should be used to map a given C type to a Perl value. -Each of the sections of the typemap must be preceded by one of the TYPEMAP, -INPUT, or OUTPUT keywords. +The section labels C, C, or C must begin +in the first column on a line by themselves, and must be in uppercase. The default typemap in the C directory of the Perl source contains many useful types which can be used by Perl extensions. Some extensions define