{ "content": [ { "type": "text", "text": "# perlxs (perldoc)\n\n## NAME\n\nperlxs - XS language reference manual\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION** (53 subsections)\n- **EXAMPLES**\n- **CAVEATS**\n- **XS VERSION**\n- **AUTHOR**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "perlxs", "section": "", "mode": "perldoc", "summary": "perlxs - XS language reference manual", "synopsis": null, "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [ "File \"RPC.xs\": Interface to some ONC+ RPC bind library functions.", "#define PERLNOGETCONTEXT", "#include \"EXTERN.h\"", "#include \"perl.h\"", "#include \"XSUB.h\"", "/* Note: On glibc 2.13 and earlier, this needs be */", "#include ", "typedef struct netconfig Netconfig;", "MODULE = RPC PACKAGE = RPC", "SV *", "rpcbgettime(host=\"localhost\")", "char *host", "PREINIT:", "timet timep;", "CODE:", "ST(0) = svnewmortal();", "if( rpcbgettime( host, &timep ) )", "svsetnv( ST(0), (double)timep );", "Netconfig *", "getnetconfigent(netid=\"udp\")", "char *netid", "MODULE = RPC PACKAGE = NetconfigPtr PREFIX = rpcb", "void", "rpcbDESTROY(netconf)", "Netconfig *netconf", "CODE:", "printf(\"NetconfigPtr::DESTROY\\n\");", "free( netconf );", "File \"typemap\": Custom typemap for RPC.xs. (cf. perlxstypemap)", "TYPEMAP", "Netconfig * TPTROBJ", "File \"RPC.pm\": Perl module for the RPC extension.", "package RPC;", "require Exporter;", "require DynaLoader;", "@ISA = qw(Exporter DynaLoader);", "@EXPORT = qw(rpcbgettime getnetconfigent);", "bootstrap RPC;", "1;", "File \"rpctest.pl\": Perl test program for the RPC extension.", "use RPC;", "$netconf = getnetconfigent();", "$a = rpcbgettime();", "print \"time = $a\\n\";", "print \"netconf = $netconf\\n\";", "$netconf = getnetconfigent(\"tcp\");", "$a = rpcbgettime(\"poplar\");", "print \"time = $a\\n\";", "print \"netconf = $netconf\\n\";", "In Makefile.PL add -ltirpc and -I/usr/include/tirpc." ], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 1, "subsections": [ { "name": "Introduction", "lines": 63 }, { "name": "On The Road", "lines": 68 }, { "name": "The Anatomy of an XSUB", "lines": 68 }, { "name": "The Argument Stack", "lines": 13 }, { "name": "The RETVAL Variable", "lines": 21 }, { "name": "Returning SVs, AVs and HVs through RETVAL", "lines": 58 }, { "name": "The MODULE Keyword", "lines": 13 }, { "name": "The PACKAGE Keyword", "lines": 22 }, { "name": "The PREFIX Keyword", "lines": 11 }, { "name": "The OUTPUT: Keyword", "lines": 3 }, { "name": "sin", "lines": 36 }, { "name": "The NOOUTPUT Keyword", "lines": 21 }, { "name": "The CODE: Keyword", "lines": 21 }, { "name": "The INIT: Keyword", "lines": 26 }, { "name": "The NOINIT Keyword", "lines": 16 }, { "name": "The TYPEMAP: Keyword", "lines": 14 }, { "name": "Initializing Function Parameters", "lines": 47 }, { "name": "Default Parameter Values", "lines": 14 }, { "name": "rpcb_gettime", "lines": 10 }, { "name": "The PREINIT: Keyword", "lines": 72 }, { "name": "mutate", "lines": 19 }, { "name": "The SCOPE: Keyword", "lines": 14 }, { "name": "The INPUT: Keyword", "lines": 160 }, { "name": "Variable-length Parameter Lists", "lines": 29 }, { "name": "The CARGS: Keyword", "lines": 22 }, { "name": "The PPCODE: Keyword", "lines": 56 }, { "name": "Returning Undef And Empty Lists", "lines": 10 }, { "name": "sv_newmortal", "lines": 77 }, { "name": "The REQUIRE: Keyword", "lines": 6 }, { "name": "The CLEANUP: Keyword", "lines": 5 }, { "name": "The POSTCALL: Keyword", "lines": 9 }, { "name": "The BOOT: Keyword", "lines": 13 }, { "name": "The VERSIONCHECK: Keyword", "lines": 18 }, { "name": "The PROTOTYPES: Keyword", "lines": 16 }, { "name": "The PROTOTYPE: Keyword", "lines": 27 }, { "name": "The ALIAS: Keyword", "lines": 20 }, { "name": "The OVERLOAD: Keyword", "lines": 33 }, { "name": "The FALLBACK: Keyword", "lines": 13 }, { "name": "The INTERFACE: Keyword", "lines": 34 }, { "name": "The INTERFACEMACRO: Keyword", "lines": 9 }, { "name": "subtract", "lines": 22 }, { "name": "The INCLUDE: Keyword", "lines": 27 }, { "name": "The INCLUDECOMMAND: Keyword", "lines": 8 }, { "name": "The CASE: Keyword", "lines": 42 }, { "name": "The EXPORTXSUBSYMBOLS: Keyword", "lines": 46 }, { "name": "Inserting POD, Comments and C Preprocessor Directives", "lines": 130 }, { "name": "Interface Strategy", "lines": 44 }, { "name": "Perl Objects And C Structures", "lines": 7 }, { "name": "getnetconfigent", "lines": 46 }, { "name": "getnetconfigent", "lines": 1 }, { "name": "Safely Storing Static Data in XS", "lines": 147 }, { "name": "dMY_CXT_INTERP", "lines": 5 }, { "name": "Thread-aware system interfaces", "lines": 18 } ] }, { "name": "EXAMPLES", "lines": 70, "subsections": [] }, { "name": "CAVEATS", "lines": 152, "subsections": [] }, { "name": "XS VERSION", "lines": 2, "subsections": [] }, { "name": "AUTHOR", "lines": 4, "subsections": [] } ], "sections": { "NAME": { "content": "perlxs - XS language reference manual\n", "subsections": [] }, "DESCRIPTION": { "content": "", "subsections": [ { "name": "Introduction", "content": "XS is an interface description file format used to create an extension interface between Perl\nand C code (or a C library) which one wishes to use with Perl. The XS interface is combined with\nthe library to create a new library which can then be either dynamically loaded or statically\nlinked into perl. The XS interface description is written in the XS language and is the core\ncomponent of the Perl extension interface.\n\nBefore writing XS, read the \"CAVEATS\" section below.\n\nAn XSUB forms the basic unit of the XS interface. After compilation by the xsubpp compiler, each\nXSUB amounts to a C function definition which will provide the glue between Perl calling\nconventions and C calling conventions.\n\nThe glue code pulls the arguments from the Perl stack, converts these Perl values to the formats\nexpected by a C function, call this C function, transfers the return values of the C function\nback to Perl. Return values here may be a conventional C return value or any C function\narguments that may serve as output parameters. These return values may be passed back to Perl\neither by putting them on the Perl stack, or by modifying the arguments supplied from the Perl\nside.\n\nThe above is a somewhat simplified view of what really happens. Since Perl allows more flexible\ncalling conventions than C, XSUBs may do much more in practice, such as checking input\nparameters for validity, throwing exceptions (or returning undef/empty list) if the return value\nfrom the C function indicates failure, calling different C functions based on numbers and types\nof the arguments, providing an object-oriented interface, etc.\n\nOf course, one could write such glue code directly in C. However, this would be a tedious task,\nespecially if one needs to write glue for multiple C functions, and/or one is not familiar\nenough with the Perl stack discipline and other such arcana. XS comes to the rescue here:\ninstead of writing this glue C code in long-hand, one can write a more concise short-hand\n*description* of what should be done by the glue, and let the XS compiler xsubpp handle the\nrest.\n\nThe XS language allows one to describe the mapping between how the C routine is used, and how\nthe corresponding Perl routine is used. It also allows creation of Perl routines which are\ndirectly translated to C code and which are not related to a pre-existing C function. In cases\nwhen the C interface coincides with the Perl interface, the XSUB declaration is almost identical\nto a declaration of a C function (in K&R style). In such circumstances, there is another tool\ncalled \"h2xs\" that is able to translate an entire C header file into a corresponding XS file\nthat will provide glue to the functions/macros described in the header file.\n\nThe XS compiler is called xsubpp. This compiler creates the constructs necessary to let an XSUB\nmanipulate Perl values, and creates the glue necessary to let Perl call the XSUB. The compiler\nuses typemaps to determine how to map C function parameters and output values to Perl values and\nback. The default typemap (which comes with Perl) handles many common C types. A supplementary\ntypemap may also be needed to handle any special structures and types for the library being\nlinked. For more information on typemaps, see perlxstypemap.\n\nA file in XS format starts with a C language section which goes until the first \"MODULE =\"\ndirective. Other XS directives and XSUB definitions may follow this line. The \"language\" used in\nthis part of the file is usually referred to as the XS language. xsubpp recognizes and skips POD\n(see perlpod) in both the C and XS language sections, which allows the XS file to contain\nembedded documentation.\n\nSee perlxstut for a tutorial on the whole extension creation process.\n\nNote: For some extensions, Dave Beazley's SWIG system may provide a significantly more\nconvenient mechanism for creating the extension glue code. See for more\ninformation.\n\nFor simple bindings to C libraries as well as other machine code libraries, consider instead\nusing the much simpler libffi interface via CPAN modules like\nFFI::Platypus or FFI::Raw.\n" }, { "name": "On The Road", "content": "Many of the examples which follow will concentrate on creating an interface between Perl and the\nONC+ RPC bind library functions. The rpcbgettime() function is used to demonstrate many\nfeatures of the XS language. This function has two parameters; the first is an input parameter\nand the second is an output parameter. The function also returns a status value.\n\nboolt rpcbgettime(const char *host, timet *timep);\n\nFrom C this function will be called with the following statements.\n\n#include \nboolt status;\ntimet timep;\nstatus = rpcbgettime( \"localhost\", &timep );\n\nIf an XSUB is created to offer a direct translation between this function and Perl, then this\nXSUB will be used from Perl with the following code. The $status and $timep variables will\ncontain the output of the function.\n\nuse RPC;\n$status = rpcbgettime( \"localhost\", $timep );\n\nThe following XS file shows an XS subroutine, or XSUB, which demonstrates one possible interface\nto the rpcbgettime() function. This XSUB represents a direct translation between C and Perl and\nso preserves the interface even from Perl. This XSUB will be invoked from Perl with the usage\nshown above. Note that the first three #include statements, for \"EXTERN.h\", \"perl.h\", and\n\"XSUB.h\", will always be present at the beginning of an XS file. This approach and others will\nbe expanded later in this document. A #define for \"PERLNOGETCONTEXT\" should be present to\nfetch the interpreter context more efficiently, see perlguts for details.\n\n#define PERLNOGETCONTEXT\n#include \"EXTERN.h\"\n#include \"perl.h\"\n#include \"XSUB.h\"\n#include \n\nMODULE = RPC PACKAGE = RPC\n\nboolt\nrpcbgettime(host,timep)\nchar *host\ntimet &timep\nOUTPUT:\ntimep\n\nAny extension to Perl, including those containing XSUBs, should have a Perl module to serve as\nthe bootstrap which pulls the extension into Perl. This module will export the extension's\nfunctions and variables to the Perl program and will cause the extension's XSUBs to be linked\ninto Perl. The following module will be used for most of the examples in this document and\nshould be used from Perl with the \"use\" command as shown earlier. Perl modules are explained in\nmore detail later in this document.\n\npackage RPC;\n\nrequire Exporter;\nrequire DynaLoader;\n@ISA = qw(Exporter DynaLoader);\n@EXPORT = qw( rpcbgettime );\n\nbootstrap RPC;\n1;\n\nThroughout this document a variety of interfaces to the rpcbgettime() XSUB will be explored.\nThe XSUBs will take their parameters in different orders or will take different numbers of\nparameters. In each case the XSUB is an abstraction between Perl and the real C rpcbgettime()\nfunction, and the XSUB must always ensure that the real rpcbgettime() function is called with\nthe correct parameters. This abstraction will allow the programmer to create a more Perl-like\ninterface to the C function.\n" }, { "name": "The Anatomy of an XSUB", "content": "The simplest XSUBs consist of 3 parts: a description of the return value, the name of the XSUB\nroutine and the names of its arguments, and a description of types or formats of the arguments.\n\nThe following XSUB allows a Perl program to access a C library function called sin(). The XSUB\nwill imitate the C function which takes a single argument and returns a single value.\n\ndouble\nsin(x)\ndouble x\n\nOptionally, one can merge the description of types and the list of argument names, rewriting\nthis as\n\ndouble\nsin(double x)\n\nThis makes this XSUB look similar to an ANSI C declaration. An optional semicolon is allowed\nafter the argument list, as in\n\ndouble\nsin(double x);\n\nParameters with C pointer types can have different semantic: C functions with similar\ndeclarations\n\nbool stringlooksasanumber(char *s);\nbool makecharuppercase(char *c);\n\nare used in absolutely incompatible manner. Parameters to these functions could be described\nxsubpp like this:\n\nchar * s\nchar &c\n\nBoth these XS declarations correspond to the \"char*\" C type, but they have different semantics,\nsee \"The & Unary Operator\".\n\nIt is convenient to think that the indirection operator \"*\" should be considered as a part of\nthe type and the address operator \"&\" should be considered part of the variable. See\nperlxstypemap for more info about handling qualifiers and unary operators in C types.\n\nThe function name and the return type must be placed on separate lines and should be flush\nleft-adjusted.\n\nINCORRECT CORRECT\n\ndouble sin(x) double\ndouble x sin(x)\ndouble x\n\nThe rest of the function description may be indented or left-adjusted. The following example\nshows a function with its body left-adjusted. Most examples in this document will indent the\nbody for better readability.\n\nCORRECT\n\ndouble\nsin(x)\ndouble x\n\nMore complicated XSUBs may contain many other sections. Each section of an XSUB starts with the\ncorresponding keyword, such as INIT: or CLEANUP:. However, the first two lines of an XSUB always\ncontain the same data: descriptions of the return type and the names of the function and its\nparameters. Whatever immediately follows these is considered to be an INPUT: section unless\nexplicitly marked with another keyword. (See \"The INPUT: Keyword\".)\n\nAn XSUB section continues until another section-start keyword is found.\n" }, { "name": "The Argument Stack", "content": "The Perl argument stack is used to store the values which are sent as parameters to the XSUB and\nto store the XSUB's return value(s). In reality all Perl functions (including non-XSUB ones)\nkeep their values on this stack all the same time, each limited to its own range of positions on\nthe stack. In this document the first position on that stack which belongs to the active\nfunction will be referred to as position 0 for that function.\n\nXSUBs refer to their stack arguments with the macro ST(x), where *x* refers to a position in\nthis XSUB's part of the stack. Position 0 for that function would be known to the XSUB as ST(0).\nThe XSUB's incoming parameters and outgoing return values always begin at ST(0). For many simple\ncases the xsubpp compiler will generate the code necessary to handle the argument stack by\nembedding code fragments found in the typemaps. In more complex cases the programmer must supply\nthe code.\n" }, { "name": "The RETVAL Variable", "content": "The RETVAL variable is a special C variable that is declared automatically for you. The C type\nof RETVAL matches the return type of the C library function. The xsubpp compiler will declare\nthis variable in each XSUB with non-\"void\" return type. By default the generated C function will\nuse RETVAL to hold the return value of the C library function being called. In simple cases the\nvalue of RETVAL will be placed in ST(0) of the argument stack where it can be received by Perl\nas the return value of the XSUB.\n\nIf the XSUB has a return type of \"void\" then the compiler will not declare a RETVAL variable for\nthat function. When using a PPCODE: section no manipulation of the RETVAL variable is required,\nthe section may use direct stack manipulation to place output values on the stack.\n\nIf PPCODE: directive is not used, \"void\" return value should be used only for subroutines which\ndo not return a value, *even if* CODE: directive is used which sets ST(0) explicitly.\n\nOlder versions of this document recommended to use \"void\" return value in such cases. It was\ndiscovered that this could lead to segfaults in cases when XSUB was *truly* \"void\". This\npractice is now deprecated, and may be not supported at some future version. Use the return\nvalue \"SV *\" in such cases. (Currently \"xsubpp\" contains some heuristic code which tries to\ndisambiguate between \"truly-void\" and \"old-practice-declared-as-void\" functions. Hence your code\nis at mercy of this heuristics unless you use \"SV *\" as return value.)\n" }, { "name": "Returning SVs, AVs and HVs through RETVAL", "content": "When you're using RETVAL to return an \"SV *\", there's some magic going on behind the scenes that\nshould be mentioned. When you're manipulating the argument stack using the ST(x) macro, for\nexample, you usually have to pay special attention to reference counts. (For more about\nreference counts, see perlguts.) To make your life easier, the typemap file automatically makes\n\"RETVAL\" mortal when you're returning an \"SV *\". Thus, the following two XSUBs are more or less\nequivalent:\n\nvoid\nalpha()\nPPCODE:\nST(0) = newSVpv(\"Hello World\",0);\nsv2mortal(ST(0));\nXSRETURN(1);\n\nSV *\nbeta()\nCODE:\nRETVAL = newSVpv(\"Hello World\",0);\nOUTPUT:\nRETVAL\n\nThis is quite useful as it usually improves readability. While this works fine for an \"SV *\",\nit's unfortunately not as easy to have \"AV *\" or \"HV *\" as a return value. You *should* be able\nto write:\n\nAV *\narray()\nCODE:\nRETVAL = newAV();\n/* do something with RETVAL */\nOUTPUT:\nRETVAL\n\nBut due to an unfixable bug (fixing it would break lots of existing CPAN modules) in the typemap\nfile, the reference count of the \"AV *\" is not properly decremented. Thus, the above XSUB would\nleak memory whenever it is being called. The same problem exists for \"HV *\", \"CV *\", and \"SVREF\"\n(which indicates a scalar reference, not a general \"SV *\"). In XS code on perls starting with\nperl 5.16, you can override the typemaps for any of these types with a version that has proper\nhandling of refcounts. In your \"TYPEMAP\" section, do\n\nAV* TAVREFREFCOUNTFIXED\n\nto get the repaired variant. For backward compatibility with older versions of perl, you can\ninstead decrement the reference count manually when you're returning one of the aforementioned\ntypes using \"sv2mortal\":\n\nAV *\narray()\nCODE:\nRETVAL = newAV();\nsv2mortal((SV*)RETVAL);\n/* do something with RETVAL */\nOUTPUT:\nRETVAL\n\nRemember that you don't have to do this for an \"SV *\". The reference documentation for all core\ntypemaps can be found in perlxstypemap.\n" }, { "name": "The MODULE Keyword", "content": "The MODULE keyword is used to start the XS code and to specify the package of the functions\nwhich are being defined. All text preceding the first MODULE keyword is considered C code and is\npassed through to the output with POD stripped, but otherwise untouched. Every XS module will\nhave a bootstrap function which is used to hook the XSUBs into Perl. The package name of this\nbootstrap function will match the value of the last MODULE statement in the XS source files. The\nvalue of MODULE should always remain constant within the same XS file, though this is not\nrequired.\n\nThe following example will start the XS code and will place all functions in a package named\nRPC.\n\nMODULE = RPC\n" }, { "name": "The PACKAGE Keyword", "content": "When functions within an XS source file must be separated into packages the PACKAGE keyword\nshould be used. This keyword is used with the MODULE keyword and must follow immediately after\nit when used.\n\nMODULE = RPC PACKAGE = RPC\n\n[ XS code in package RPC ]\n\nMODULE = RPC PACKAGE = RPCB\n\n[ XS code in package RPCB ]\n\nMODULE = RPC PACKAGE = RPC\n\n[ XS code in package RPC ]\n\nThe same package name can be used more than once, allowing for non-contiguous code. This is\nuseful if you have a stronger ordering principle than package names.\n\nAlthough this keyword is optional and in some cases provides redundant information it should\nalways be used. This keyword will ensure that the XSUBs appear in the desired package.\n" }, { "name": "The PREFIX Keyword", "content": "The PREFIX keyword designates prefixes which should be removed from the Perl function names. If\nthe C function is \"rpcbgettime()\" and the PREFIX value is \"rpcb\" then Perl will see this\nfunction as \"gettime()\".\n\nThis keyword should follow the PACKAGE keyword when used. If PACKAGE is not used then PREFIX\nshould follow the MODULE keyword.\n\nMODULE = RPC PREFIX = rpc\n\nMODULE = RPC PACKAGE = RPCB PREFIX = rpcb\n" }, { "name": "The OUTPUT: Keyword", "content": "The OUTPUT: keyword indicates that certain function parameters should be updated (new values\nmade visible to Perl) when the XSUB terminates or that certain values should be returned to the\ncalling Perl function. For simple functions which have no CODE: or PPCODE: section, such as the" }, { "name": "sin", "content": "more complex functions the xsubpp compiler will need help to determine which variables are\noutput variables.\n\nThis keyword will normally be used to complement the CODE: keyword. The RETVAL variable is not\nrecognized as an output variable when the CODE: keyword is present. The OUTPUT: keyword is used\nin this situation to tell the compiler that RETVAL really is an output variable.\n\nThe OUTPUT: keyword can also be used to indicate that function parameters are output variables.\nThis may be necessary when a parameter has been modified within the function and the programmer\nwould like the update to be seen by Perl.\n\nboolt\nrpcbgettime(host,timep)\nchar *host\ntimet &timep\nOUTPUT:\ntimep\n\nThe OUTPUT: keyword will also allow an output parameter to be mapped to a matching piece of code\nrather than to a typemap.\n\nboolt\nrpcbgettime(host,timep)\nchar *host\ntimet &timep\nOUTPUT:\ntimep svsetnv(ST(1), (double)timep);\n\nxsubpp emits an automatic \"SvSETMAGIC()\" for all parameters in the OUTPUT section of the XSUB,\nexcept RETVAL. This is the usually desired behavior, as it takes care of properly invoking 'set'\nmagic on output parameters (needed for hash or array element parameters that must be created if\nthey didn't exist). If for some reason, this behavior is not desired, the OUTPUT section may\ncontain a \"SETMAGIC: DISABLE\" line to disable it for the remainder of the parameters in the\nOUTPUT section. Likewise, \"SETMAGIC: ENABLE\" can be used to reenable it for the remainder of the\nOUTPUT section. See perlguts for more details about 'set' magic.\n" }, { "name": "The NOOUTPUT Keyword", "content": "The NOOUTPUT can be placed as the first token of the XSUB. This keyword indicates that while\nthe C subroutine we provide an interface to has a non-\"void\" return type, the return value of\nthis C subroutine should not be returned from the generated Perl subroutine.\n\nWith this keyword present \"The RETVAL Variable\" is created, and in the generated call to the\nsubroutine this variable is assigned to, but the value of this variable is not going to be used\nin the auto-generated code.\n\nThis keyword makes sense only if \"RETVAL\" is going to be accessed by the user-supplied code. It\nis especially useful to make a function interface more Perl-like, especially when the C return\nvalue is just an error condition indicator. For example,\n\nNOOUTPUT int\ndeletefile(char *name)\nPOSTCALL:\nif (RETVAL != 0)\ncroak(\"Error %d while deleting file '%s'\", RETVAL, name);\n\nHere the generated XS function returns nothing on success, and will die() with a meaningful\nerror message on error.\n" }, { "name": "The CODE: Keyword", "content": "This keyword is used in more complicated XSUBs which require special handling for the C\nfunction. The RETVAL variable is still declared, but it will not be returned unless it is\nspecified in the OUTPUT: section.\n\nThe following XSUB is for a C function which requires special handling of its parameters. The\nPerl usage is given first.\n\n$status = rpcbgettime( \"localhost\", $timep );\n\nThe XSUB follows.\n\nboolt\nrpcbgettime(host,timep)\nchar *host\ntimet timep\nCODE:\nRETVAL = rpcbgettime( host, &timep );\nOUTPUT:\ntimep\nRETVAL\n" }, { "name": "The INIT: Keyword", "content": "The INIT: keyword allows initialization to be inserted into the XSUB before the compiler\ngenerates the call to the C function. Unlike the CODE: keyword above, this keyword does not\naffect the way the compiler handles RETVAL.\n\nboolt\nrpcbgettime(host,timep)\nchar *host\ntimet &timep\nINIT:\nprintf(\"# Host is %s\\n\", host );\nOUTPUT:\ntimep\n\nAnother use for the INIT: section is to check for preconditions before making a call to the C\nfunction:\n\nlong long\nlldiv(a,b)\nlong long a\nlong long b\nINIT:\nif (a == 0 && b == 0)\nXSRETURNUNDEF;\nif (b == 0)\ncroak(\"lldiv: cannot divide by 0\");\n" }, { "name": "The NOINIT Keyword", "content": "The NOINIT keyword is used to indicate that a function parameter is being used only as an\noutput value. The xsubpp compiler will normally generate code to read the values of all function\nparameters from the argument stack and assign them to C variables upon entry to the function.\nNOINIT will tell the compiler that some parameters will be used for output rather than for\ninput and that they will be handled before the function terminates.\n\nThe following example shows a variation of the rpcbgettime() function. This function uses the\ntimep variable only as an output variable and does not care about its initial contents.\n\nboolt\nrpcbgettime(host,timep)\nchar *host\ntimet &timep = NOINIT\nOUTPUT:\ntimep\n" }, { "name": "The TYPEMAP: Keyword", "content": "Starting with Perl 5.16, you can embed typemaps into your XS code instead of or in addition to\ntypemaps in a separate file. Multiple such embedded typemaps will be processed in order of\nappearance in the XS code and like local typemap files take precedence over the default typemap,\nthe embedded typemaps may overwrite previous definitions of TYPEMAP, INPUT, and OUTPUT stanzas.\nThe syntax for embedded typemaps is\n\nTYPEMAP: < 1 )\nhost = (char *)SvPVbytenolen(ST(1));\nRETVAL = rpcbgettime( host, &timep );\nOUTPUT:\ntimep\nRETVAL\n" }, { "name": "The CARGS: Keyword", "content": "The CARGS: keyword allows creating of XSUBS which have different calling sequence from Perl\nthan from C, without a need to write CODE: or PPCODE: section. The contents of the CARGS:\nparagraph is put as the argument to the called C function without any change.\n\nFor example, suppose that a C function is declared as\n\nsymbolic nthderivative(int n, symbolic function, int flags);\n\nand that the default flags are kept in a global C variable \"defaultflags\". Suppose that you\nwant to create an interface which is called as\n\n$secondderiv = $function->nthderivative(2);\n\nTo do this, declare the XSUB as\n\nsymbolic\nnthderivative(function, n)\nsymbolic function\nint n\nCARGS:\nn, function, defaultflags\n" }, { "name": "The PPCODE: Keyword", "content": "The PPCODE: keyword is an alternate form of the CODE: keyword and is used to tell the xsubpp\ncompiler that the programmer is supplying the code to control the argument stack for the XSUBs\nreturn values. Occasionally one will want an XSUB to return a list of values rather than a\nsingle value. In these cases one must use PPCODE: and then explicitly push the list of values on\nthe stack. The PPCODE: and CODE: keywords should not be used together within the same XSUB.\n\nThe actual difference between PPCODE: and CODE: sections is in the initialization of \"SP\" macro\n(which stands for the *current* Perl stack pointer), and in the handling of data on the stack\nwhen returning from an XSUB. In CODE: sections SP preserves the value which was on entry to the\nXSUB: SP is on the function pointer (which follows the last parameter). In PPCODE: sections SP\nis moved backward to the beginning of the parameter list, which allows \"PUSH*()\" macros to place\noutput values in the place Perl expects them to be when the XSUB returns back to Perl.\n\nThe generated trailer for a CODE: section ensures that the number of return values Perl will see\nis either 0 or 1 (depending on the \"void\"ness of the return value of the C function, and\nheuristics mentioned in \"The RETVAL Variable\"). The trailer generated for a PPCODE: section is\nbased on the number of return values and on the number of times \"SP\" was updated by \"[X]PUSH*()\"\nmacros.\n\nNote that macros ST(i), \"XSTm*()\" and \"XSRETURN*()\" work equally well in CODE: sections and\nPPCODE: sections.\n\nThe following XSUB will call the C rpcbgettime() function and will return its two output\nvalues, timep and status, to Perl as a single list.\n\nvoid\nrpcbgettime(host)\nchar *host\nPREINIT:\ntimet timep;\nboolt status;\nPPCODE:\nstatus = rpcbgettime( host, &timep );\nEXTEND(SP, 2);\nPUSHs(sv2mortal(newSViv(status)));\nPUSHs(sv2mortal(newSViv(timep)));\n\nNotice that the programmer must supply the C code necessary to have the real rpcbgettime()\nfunction called and to have the return values properly placed on the argument stack.\n\nThe \"void\" return type for this function tells the xsubpp compiler that the RETVAL variable is\nnot needed or used and that it should not be created. In most scenarios the void return type\nshould be used with the PPCODE: directive.\n\nThe EXTEND() macro is used to make room on the argument stack for 2 return values. The PPCODE:\ndirective causes the xsubpp compiler to create a stack pointer available as \"SP\", and it is this\npointer which is being used in the EXTEND() macro. The values are then pushed onto the stack\nwith the PUSHs() macro.\n\nNow the rpcbgettime() function can be used from Perl with the following statement.\n\n($status, $timep) = rpcbgettime(\"localhost\");\n\nWhen handling output parameters with a PPCODE section, be sure to handle 'set' magic properly.\nSee perlguts for details about 'set' magic.\n" }, { "name": "Returning Undef And Empty Lists", "content": "Occasionally the programmer will want to return simply \"undef\" or an empty list if a function\nfails rather than a separate status value. The rpcbgettime() function offers just this\nsituation. If the function succeeds we would like to have it return the time and if it fails we\nwould like to have undef returned. In the following Perl code the value of $timep will either be\nundef or it will be a valid time.\n\n$timep = rpcbgettime( \"localhost\" );\n\nThe following XSUB uses the \"SV *\" return type as a mnemonic only, and uses a CODE: block to\nindicate to the compiler that the programmer has supplied all the necessary code. The" }, { "name": "sv_newmortal", "content": "value.\n\nSV *\nrpcbgettime(host)\nchar * host\nPREINIT:\ntimet timep;\nboolt x;\nCODE:\nST(0) = svnewmortal();\nif( rpcbgettime( host, &timep ) )\nsvsetnv( ST(0), (double)timep);\n\nThe next example demonstrates how one would place an explicit undef in the return value, should\nthe need arise.\n\nSV *\nrpcbgettime(host)\nchar * host\nPREINIT:\ntimet timep;\nboolt x;\nCODE:\nif( rpcbgettime( host, &timep ) ){\nST(0) = svnewmortal();\nsvsetnv( ST(0), (double)timep);\n}\nelse{\nST(0) = &PLsvundef;\n}\n\nTo return an empty list one must use a PPCODE: block and then not push return values on the\nstack.\n\nvoid\nrpcbgettime(host)\nchar *host\nPREINIT:\ntimet timep;\nPPCODE:\nif( rpcbgettime( host, &timep ) )\nPUSHs(sv2mortal(newSViv(timep)));\nelse{\n/* Nothing pushed on stack, so an empty\n* list is implicitly returned. */\n}\n\nSome people may be inclined to include an explicit \"return\" in the above XSUB, rather than\nletting control fall through to the end. In those situations \"XSRETURNEMPTY\" should be used,\ninstead. This will ensure that the XSUB stack is properly adjusted. Consult perlapi for other\n\"XSRETURN\" macros.\n\nSince \"XSRETURN*\" macros can be used with CODE blocks as well, one can rewrite this example as:\n\nint\nrpcbgettime(host)\nchar *host\nPREINIT:\ntimet timep;\nCODE:\nRETVAL = rpcbgettime( host, &timep );\nif (RETVAL == 0)\nXSRETURNUNDEF;\nOUTPUT:\nRETVAL\n\nIn fact, one can put this check into a POSTCALL: section as well. Together with PREINIT:\nsimplifications, this leads to:\n\nint\nrpcbgettime(host)\nchar *host\ntimet timep;\nPOSTCALL:\nif (RETVAL == 0)\nXSRETURNUNDEF;\n" }, { "name": "The REQUIRE: Keyword", "content": "The REQUIRE: keyword is used to indicate the minimum version of the xsubpp compiler needed to\ncompile the XS module. An XS module which contains the following statement will compile with\nonly xsubpp version 1.922 or greater:\n\nREQUIRE: 1.922\n" }, { "name": "The CLEANUP: Keyword", "content": "This keyword can be used when an XSUB requires special cleanup procedures before it terminates.\nWhen the CLEANUP: keyword is used it must follow any CODE:, or OUTPUT: blocks which are present\nin the XSUB. The code specified for the cleanup block will be added as the last statements in\nthe XSUB.\n" }, { "name": "The POSTCALL: Keyword", "content": "This keyword can be used when an XSUB requires special procedures executed after the C\nsubroutine call is performed. When the POSTCALL: keyword is used it must precede OUTPUT: and\nCLEANUP: blocks which are present in the XSUB.\n\nSee examples in \"The NOOUTPUT Keyword\" and \"Returning Undef And Empty Lists\".\n\nThe POSTCALL: block does not make a lot of sense when the C subroutine call is supplied by user\nby providing either CODE: or PPCODE: section.\n" }, { "name": "The BOOT: Keyword", "content": "The BOOT: keyword is used to add code to the extension's bootstrap function. The bootstrap\nfunction is generated by the xsubpp compiler and normally holds the statements necessary to\nregister any XSUBs with Perl. With the BOOT: keyword the programmer can tell the compiler to add\nextra statements to the bootstrap function.\n\nThis keyword may be used any time after the first MODULE keyword and should appear on a line by\nitself. The first blank line after the keyword will terminate the code block.\n\nBOOT:\n# The following message will be printed when the\n# bootstrap function executes.\nprintf(\"Hello from the bootstrap!\\n\");\n" }, { "name": "The VERSIONCHECK: Keyword", "content": "The VERSIONCHECK: keyword corresponds to xsubpp's \"-versioncheck\" and \"-noversioncheck\" options.\nThis keyword overrides the command line options. Version checking is enabled by default. When\nversion checking is enabled the XS module will attempt to verify that its version matches the\nversion of the PM module.\n\nTo enable version checking:\n\nVERSIONCHECK: ENABLE\n\nTo disable version checking:\n\nVERSIONCHECK: DISABLE\n\nNote that if the version of the PM module is an NV (a floating point number), it will be\nstringified with a possible loss of precision (currently chopping to nine decimal places) so\nthat it may not match the version of the XS module anymore. Quoting the $VERSION declaration to\nmake it a string is recommended if long version numbers are used.\n" }, { "name": "The PROTOTYPES: Keyword", "content": "The PROTOTYPES: keyword corresponds to xsubpp's \"-prototypes\" and \"-noprototypes\" options. This\nkeyword overrides the command line options. Prototypes are disabled by default. When prototypes\nare enabled, XSUBs will be given Perl prototypes. This keyword may be used multiple times in an\nXS module to enable and disable prototypes for different parts of the module. Note that xsubpp\nwill nag you if you don't explicitly enable or disable prototypes, with:\n\nPlease specify prototyping behavior for Foo.xs (see perlxs manual)\n\nTo enable prototypes:\n\nPROTOTYPES: ENABLE\n\nTo disable prototypes:\n\nPROTOTYPES: DISABLE\n" }, { "name": "The PROTOTYPE: Keyword", "content": "This keyword is similar to the PROTOTYPES: keyword above but can be used to force xsubpp to use\na specific prototype for the XSUB. This keyword overrides all other prototype options and\nkeywords but affects only the current XSUB. Consult \"Prototypes\" in perlsub for information\nabout Perl prototypes.\n\nboolt\nrpcbgettime(timep, ...)\ntimet timep = NOINIT\nPROTOTYPE: $;$\nPREINIT:\nchar *host = \"localhost\";\nCODE:\nif( items > 1 )\nhost = (char *)SvPVbytenolen(ST(1));\nRETVAL = rpcbgettime( host, &timep );\nOUTPUT:\ntimep\nRETVAL\n\nIf the prototypes are enabled, you can disable it locally for a given XSUB as in the following\nexample:\n\nvoid\nrpcbgettimenoproto()\nPROTOTYPE: DISABLE\n...\n" }, { "name": "The ALIAS: Keyword", "content": "The ALIAS: keyword allows an XSUB to have two or more unique Perl names and to know which of\nthose names was used when it was invoked. The Perl names may be fully-qualified with package\nnames. Each alias is given an index. The compiler will setup a variable called \"ix\" which\ncontain the index of the alias which was used. When the XSUB is called with its declared name\n\"ix\" will be 0.\n\nThe following example will create aliases \"FOO::gettime()\" and \"BAR::getit()\" for this function.\n\nboolt\nrpcbgettime(host,timep)\nchar *host\ntimet &timep\nALIAS:\nFOO::gettime = 1\nBAR::getit = 2\nINIT:\nprintf(\"# ix = %d\\n\", ix );\nOUTPUT:\ntimep\n" }, { "name": "The OVERLOAD: Keyword", "content": "Instead of writing an overloaded interface using pure Perl, you can also use the OVERLOAD\nkeyword to define additional Perl names for your functions (like the ALIAS: keyword above).\nHowever, the overloaded functions must be defined in such a way as to accept the number of\nparameters supplied by perl's overload system. For most overload methods, it will be three\nparameters; for the \"nomethod\" function it will be four. However, the bitwise operators \"&\",\n\"|\", \"^\", and \"~\" may be called with three *or* five arguments (see overload).\n\nIf any function has the OVERLOAD: keyword, several additional lines will be defined in the c\nfile generated by xsubpp in order to register with the overload magic.\n\nSince blessed objects are actually stored as RV's, it is useful to use the typemap features to\npreprocess parameters and extract the actual SV stored within the blessed RV. See the sample for\nTPTROBJSPECIAL below.\n\nTo use the OVERLOAD: keyword, create an XS function which takes three input parameters (or use\nthe C-style '...' definition) like this:\n\nSV *\ncmp (lobj, robj, swap)\nMyModuleobj lobj\nMyModuleobj robj\nIV swap\nOVERLOAD: cmp <=>\n{ /* function defined here */}\n\nIn this case, the function will overload both of the three way comparison operators. For all\noverload operations using non-alpha characters, you must type the parameter without quoting,\nseparating multiple overloads with whitespace. Note that \"\" (the stringify overload) should be\nentered as \\\"\\\" (i.e. escaped).\n\nSince, as mentioned above, bitwise operators may take extra arguments, you may want to use\nsomething like \"(lobj, robj, swap, ...)\" (with literal \"...\") as your parameter list.\n" }, { "name": "The FALLBACK: Keyword", "content": "In addition to the OVERLOAD keyword, if you need to control how Perl autogenerates missing\noverloaded operators, you can set the FALLBACK keyword in the module header section, like this:\n\nMODULE = RPC PACKAGE = RPC\n\nFALLBACK: TRUE\n...\n\nwhere FALLBACK can take any of the three values TRUE, FALSE, or UNDEF. If you do not set any\nFALLBACK value when using OVERLOAD, it defaults to UNDEF. FALLBACK is not used except when one\nor more functions using OVERLOAD have been defined. Please see \"fallback\" in overload for more\ndetails.\n" }, { "name": "The INTERFACE: Keyword", "content": "This keyword declares the current XSUB as a keeper of the given calling signature. If some text\nfollows this keyword, it is considered as a list of functions which have this signature, and\nshould be attached to the current XSUB.\n\nFor example, if you have 4 C functions multiply(), divide(), add(), subtract() all having the\nsignature:\n\nsymbolic f(symbolic, symbolic);\n\nyou can make them all to use the same XSUB using this:\n\nsymbolic\ninterfacesss(arg1, arg2)\nsymbolic arg1\nsymbolic arg2\nINTERFACE:\nmultiply divide\nadd subtract\n\n(This is the complete XSUB code for 4 Perl functions!) Four generated Perl function share names\nwith corresponding C functions.\n\nThe advantage of this approach comparing to ALIAS: keyword is that there is no need to code a\nswitch statement, each Perl function (which shares the same XSUB) knows which C function it\nshould call. Additionally, one can attach an extra function remainder() at runtime by using\n\nCV *mycv = newXSproto(\"Symbolic::remainder\",\nXSSymbolicinterfacesss, FILE, \"$$\");\nXSINTERFACEFUNCSET(mycv, remainder);\n\nsay, from another XSUB. (This example supposes that there was no INTERFACEMACRO: section,\notherwise one needs to use something else instead of \"XSINTERFACEFUNCSET\", see the next\nsection.)\n" }, { "name": "The INTERFACEMACRO: Keyword", "content": "This keyword allows one to define an INTERFACE using a different way to extract a function\npointer from an XSUB. The text which follows this keyword should give the name of macros which\nwould extract/set a function pointer. The extractor macro is given return type, \"CV*\", and\n\"XSANY.anydptr\" for this \"CV*\". The setter macro is given cv, and the function pointer.\n\nThe default value is \"XSINTERFACEFUNC\" and \"XSINTERFACEFUNCSET\". An INTERFACE keyword with an\nempty list of functions can be omitted if INTERFACEMACRO keyword is used.\n\nSuppose that in the previous example functions pointers for multiply(), divide(), add()," }, { "name": "subtract", "content": "\"addoff\", \"subtractoff\". Then one can use\n\n#define XSINTERFACEFUNCBYOFFSET(ret,cv,f) \\\n((XSINTERFACECVTANON(ret))fp[CvXSUBANY(cv).anyi32])\n#define XSINTERFACEFUNCBYOFFSETset(cv,f) \\\nCvXSUBANY(cv).anyi32 = CAT2( f, off )\n\nin C section,\n\nsymbolic\ninterfacesss(arg1, arg2)\nsymbolic arg1\nsymbolic arg2\nINTERFACEMACRO:\nXSINTERFACEFUNCBYOFFSET\nXSINTERFACEFUNCBYOFFSETset\nINTERFACE:\nmultiply divide\nadd subtract\n\nin XSUB section.\n" }, { "name": "The INCLUDE: Keyword", "content": "This keyword can be used to pull other files into the XS module. The other files may have XS\ncode. INCLUDE: can also be used to run a command to generate the XS code to be pulled into the\nmodule.\n\nThe file Rpcb1.xsh contains our \"rpcbgettime()\" function:\n\nboolt\nrpcbgettime(host,timep)\nchar *host\ntimet &timep\nOUTPUT:\ntimep\n\nThe XS module can use INCLUDE: to pull that file into it.\n\nINCLUDE: Rpcb1.xsh\n\nIf the parameters to the INCLUDE: keyword are followed by a pipe (\"|\") then the compiler will\ninterpret the parameters as a command. This feature is mildly deprecated in favour of the\n\"INCLUDECOMMAND:\" directive, as documented below.\n\nINCLUDE: cat Rpcb1.xsh |\n\nDo not use this to run perl: \"INCLUDE: perl |\" will run the perl that happens to be the first in\nyour path and not necessarily the same perl that is used to run \"xsubpp\". See \"The\nINCLUDECOMMAND: Keyword\".\n" }, { "name": "The INCLUDECOMMAND: Keyword", "content": "Runs the supplied command and includes its output into the current XS document.\n\"INCLUDECOMMAND\" assigns special meaning to the $^X token in that it runs the same perl\ninterpreter that is running \"xsubpp\":\n\nINCLUDECOMMAND: cat Rpcb1.xsh\n\nINCLUDECOMMAND: $^X -e ...\n" }, { "name": "The CASE: Keyword", "content": "The CASE: keyword allows an XSUB to have multiple distinct parts with each part acting as a\nvirtual XSUB. CASE: is greedy and if it is used then all other XS keywords must be contained\nwithin a CASE:. This means nothing may precede the first CASE: in the XSUB and anything\nfollowing the last CASE: is included in that case.\n\nA CASE: might switch via a parameter of the XSUB, via the \"ix\" ALIAS: variable (see \"The ALIAS:\nKeyword\"), or maybe via the \"items\" variable (see \"Variable-length Parameter Lists\"). The last\nCASE: becomes the default case if it is not associated with a conditional. The following example\nshows CASE switched via \"ix\" with a function \"rpcbgettime()\" having an alias \"xgettime()\".\nWhen the function is called as \"rpcbgettime()\" its parameters are the usual \"(char *host,\ntimet *timep)\", but when the function is called as \"xgettime()\" its parameters are reversed,\n\"(timet *timep, char *host)\".\n\nlong\nrpcbgettime(a,b)\nCASE: ix == 1\nALIAS:\nxgettime = 1\nINPUT:\n# 'a' is timep, 'b' is host\nchar *b\ntimet a = NOINIT\nCODE:\nRETVAL = rpcbgettime( b, &a );\nOUTPUT:\na\nRETVAL\nCASE:\n# 'a' is host, 'b' is timep\nchar *a\ntimet &b = NOINIT\nOUTPUT:\nb\nRETVAL\n\nThat function can be called with either of the following statements. Note the different argument\nlists.\n\n$status = rpcbgettime( $host, $timep );\n\n$status = xgettime( $timep, $host );\n" }, { "name": "The EXPORTXSUBSYMBOLS: Keyword", "content": "The EXPORTXSUBSYMBOLS: keyword is likely something you will never need. In perl versions\nearlier than 5.16.0, this keyword does nothing. Starting with 5.16, XSUB symbols are no longer\nexported by default. That is, they are \"static\" functions. If you include\n\nEXPORTXSUBSYMBOLS: ENABLE\n\nin your XS code, the XSUBs following this line will not be declared \"static\". You can later\ndisable this with\n\nEXPORTXSUBSYMBOLS: DISABLE\n\nwhich, again, is the default that you should probably never change. You cannot use this keyword\non versions of perl before 5.16 to make XSUBs \"static\".\n\nThe & Unary Operator\nThe \"&\" unary operator in the INPUT: section is used to tell xsubpp that it should convert a\nPerl value to/from C using the C type to the left of \"&\", but provide a pointer to this value\nwhen the C function is called.\n\nThis is useful to avoid a CODE: block for a C function which takes a parameter by reference.\nTypically, the parameter should be not a pointer type (an \"int\" or \"long\" but not an \"int*\" or\n\"long*\").\n\nThe following XSUB will generate incorrect C code. The xsubpp compiler will turn this into code\nwhich calls \"rpcbgettime()\" with parameters \"(char *host, timet timep)\", but the real\n\"rpcbgettime()\" wants the \"timep\" parameter to be of type \"timet*\" rather than \"timet\".\n\nboolt\nrpcbgettime(host,timep)\nchar *host\ntimet timep\nOUTPUT:\ntimep\n\nThat problem is corrected by using the \"&\" operator. The xsubpp compiler will now turn this into\ncode which calls \"rpcbgettime()\" correctly with parameters \"(char *host, timet *timep)\". It\ndoes this by carrying the \"&\" through, so the function call looks like \"rpcbgettime(host,\n&timep)\".\n\nboolt\nrpcbgettime(host,timep)\nchar *host\ntimet &timep\nOUTPUT:\ntimep\n" }, { "name": "Inserting POD, Comments and C Preprocessor Directives", "content": "C preprocessor directives are allowed within BOOT:, PREINIT: INIT:, CODE:, PPCODE:, POSTCALL:,\nand CLEANUP: blocks, as well as outside the functions. Comments are allowed anywhere after the\nMODULE keyword. The compiler will pass the preprocessor directives through untouched and will\nremove the commented lines. POD documentation is allowed at any point, both in the C and XS\nlanguage sections. POD must be terminated with a \"=cut\" command; \"xsubpp\" will exit with an\nerror if it does not. It is very unlikely that human generated C code will be mistaken for POD,\nas most indenting styles result in whitespace in front of any line starting with \"=\". Machine\ngenerated XS files may fall into this trap unless care is taken to ensure that a space breaks\nthe sequence \"\\n=\".\n\nComments can be added to XSUBs by placing a \"#\" as the first non-whitespace of a line. Care\nshould be taken to avoid making the comment look like a C preprocessor directive, lest it be\ninterpreted as such. The simplest way to prevent this is to put whitespace in front of the \"#\".\n\nIf you use preprocessor directives to choose one of two versions of a function, use\n\n#if ... version1\n#else /* ... version2 */\n#endif\n\nand not\n\n#if ... version1\n#endif\n#if ... version2\n#endif\n\nbecause otherwise xsubpp will believe that you made a duplicate definition of the function.\nAlso, put a blank line before the #else/#endif so it will not be seen as part of the function\nbody.\n\nUsing XS With C++\nIf an XSUB name contains \"::\", it is considered to be a C++ method. The generated Perl function\nwill assume that its first argument is an object pointer. The object pointer will be stored in a\nvariable called THIS. The object should have been created by C++ with the new() function and\nshould be blessed by Perl with the svsetrefpv() macro. The blessing of the object by Perl can\nbe handled by a typemap. An example typemap is shown at the end of this section.\n\nIf the return type of the XSUB includes \"static\", the method is considered to be a static\nmethod. It will call the C++ function using the class::method() syntax. If the method is not\nstatic the function will be called using the THIS->method() syntax.\n\nThe next examples will use the following C++ class.\n\nclass color {\npublic:\ncolor();\n~color();\nint blue();\nvoid setblue( int );\n\nprivate:\nint cblue;\n};\n\nThe XSUBs for the blue() and setblue() methods are defined with the class name but the\nparameter for the object (THIS, or \"self\") is implicit and is not listed.\n\nint\ncolor::blue()\n\nvoid\ncolor::setblue( val )\nint val\n\nBoth Perl functions will expect an object as the first parameter. In the generated C++ code the\nobject is called \"THIS\", and the method call will be performed on this object. So in the C++\ncode the blue() and setblue() methods will be called as this:\n\nRETVAL = THIS->blue();\n\nTHIS->setblue( val );\n\nYou could also write a single get/set method using an optional argument:\n\nint\ncolor::blue( val = NOINIT )\nint val\nPROTOTYPE $;$\nCODE:\nif (items > 1)\nTHIS->setblue( val );\nRETVAL = THIS->blue();\nOUTPUT:\nRETVAL\n\nIf the function's name is DESTROY then the C++ \"delete\" function will be called and \"THIS\" will\nbe given as its parameter. The generated C++ code for\n\nvoid\ncolor::DESTROY()\n\nwill look like this:\n\ncolor *THIS = ...; // Initialized as in typemap\n\ndelete THIS;\n\nIf the function's name is new then the C++ \"new\" function will be called to create a dynamic C++\nobject. The XSUB will expect the class name, which will be kept in a variable called \"CLASS\", to\nbe given as the first argument.\n\ncolor *\ncolor::new()\n\nThe generated C++ code will call \"new\".\n\nRETVAL = new color();\n\nThe following is an example of a typemap that could be used for this C++ example.\n\nTYPEMAP\ncolor * OOBJECT\n\nOUTPUT\n# The Perl object is blessed into 'CLASS', which should be a\n# char* having the name of the package for the blessing.\nOOBJECT\nsvsetrefpv( $arg, CLASS, (void*)$var );\n\nINPUT\nOOBJECT\nif( svisobject($arg) && (SvTYPE(SvRV($arg)) == SVtPVMG) )\n$var = ($type)SvIV((SV*)SvRV( $arg ));\nelse{\nwarn(\\\"${Package}::$funcname() -- \\\"\n\\\"$var is not a blessed SV reference\\\");\nXSRETURNUNDEF;\n}\n" }, { "name": "Interface Strategy", "content": "When designing an interface between Perl and a C library a straight translation from C to XS\n(such as created by \"h2xs -x\") is often sufficient. However, sometimes the interface will look\nvery C-like and occasionally nonintuitive, especially when the C function modifies one of its\nparameters, or returns failure inband (as in \"negative return values mean failure\"). In cases\nwhere the programmer wishes to create a more Perl-like interface the following strategy may help\nto identify the more critical parts of the interface.\n\nIdentify the C functions with input/output or output parameters. The XSUBs for these functions\nmay be able to return lists to Perl.\n\nIdentify the C functions which use some inband info as an indication of failure. They may be\ncandidates to return undef or an empty list in case of failure. If the failure may be detected\nwithout a call to the C function, you may want to use an INIT: section to report the failure.\nFor failures detectable after the C function returns one may want to use a POSTCALL: section to\nprocess the failure. In more complicated cases use CODE: or PPCODE: sections.\n\nIf many functions use the same failure indication based on the return value, you may want to\ncreate a special typedef to handle this situation. Put\n\ntypedef int negativeisfailure;\n\nnear the beginning of XS file, and create an OUTPUT typemap entry for \"negativeisfailure\"\nwhich converts negative values to \"undef\", or maybe croak()s. After this the return value of\ntype \"negativeisfailure\" will create more Perl-like interface.\n\nIdentify which values are used by only the C and XSUB functions themselves, say, when a\nparameter to a function should be a contents of a global variable. If Perl does not need to\naccess the contents of the value then it may not be necessary to provide a translation for that\nvalue from C to Perl.\n\nIdentify the pointers in the C function parameter lists and return values. Some pointers may be\nused to implement input/output or output parameters, they can be handled in XS with the \"&\"\nunary operator, and, possibly, using the NOINIT keyword. Some others will require handling of\ntypes like \"int *\", and one needs to decide what a useful Perl translation will do in such a\ncase. When the semantic is clear, it is advisable to put the translation into a typemap file.\n\nIdentify the structures used by the C functions. In many cases it may be helpful to use the\nTPTROBJ typemap for these structures so they can be manipulated by Perl as blessed objects.\n(This is handled automatically by \"h2xs -x\".)\n\nIf the same C type is used in several different contexts which require different translations,\n\"typedef\" several new types mapped to this C type, and create separate typemap entries for these\nnew types. Use these types in declarations of return type and parameters to XSUBs.\n" }, { "name": "Perl Objects And C Structures", "content": "When dealing with C structures one should select either TPTROBJ or TPTRREF for the XS type.\nBoth types are designed to handle pointers to complex objects. The TPTRREF type will allow the\nPerl object to be unblessed while the TPTROBJ type requires that the object be blessed. By\nusing TPTROBJ one can achieve a form of type-checking because the XSUB will attempt to verify\nthat the Perl object is of the expected type.\n\nThe following XS code shows the getnetconfigent() function which is used with ONC+ TIRPC. The" }, { "name": "getnetconfigent", "content": "below. The example will demonstrate how the C pointer will become a Perl reference. Perl will\nconsider this reference to be a pointer to a blessed object and will attempt to call a\ndestructor for the object. A destructor will be provided in the XS source to free the memory\nused by getnetconfigent(). Destructors in XS can be created by specifying an XSUB function whose\nname ends with the word DESTROY. XS destructors can be used to free memory which may have been\nmalloc'd by another XSUB.\n\nstruct netconfig *getnetconfigent(const char *netid);\n\nA \"typedef\" will be created for \"struct netconfig\". The Perl object will be blessed in a class\nmatching the name of the C type, with the tag \"Ptr\" appended, and the name should not have\nembedded spaces if it will be a Perl package name. The destructor will be placed in a class\ncorresponding to the class of the object and the PREFIX keyword will be used to trim the name to\nthe word DESTROY as Perl will expect.\n\ntypedef struct netconfig Netconfig;\n\nMODULE = RPC PACKAGE = RPC\n\nNetconfig *\ngetnetconfigent(netid)\nchar *netid\n\nMODULE = RPC PACKAGE = NetconfigPtr PREFIX = rpcb\n\nvoid\nrpcbDESTROY(netconf)\nNetconfig *netconf\nCODE:\nprintf(\"Now in NetconfigPtr::DESTROY\\n\");\nfree( netconf );\n\nThis example requires the following typemap entry. Consult perlxstypemap for more information\nabout adding new typemaps for an extension.\n\nTYPEMAP\nNetconfig * TPTROBJ\n\nThis example will be used with the following Perl statements.\n\nuse RPC;\n$netconf = getnetconfigent(\"udp\");\n\nWhen Perl destroys the object referenced by $netconf it will send the object to the supplied\nXSUB DESTROY function. Perl cannot determine, and does not care, that this object is a C struct\nand not a Perl object. In this sense, there is no difference between the object created by the" }, { "name": "getnetconfigent", "content": "" }, { "name": "Safely Storing Static Data in XS", "content": "Starting with Perl 5.8, a macro framework has been defined to allow static data to be safely\nstored in XS modules that will be accessed from a multi-threaded Perl.\n\nAlthough primarily designed for use with multi-threaded Perl, the macros have been designed so\nthat they will work with non-threaded Perl as well.\n\nIt is therefore strongly recommended that these macros be used by all XS modules that make use\nof static data.\n\nThe easiest way to get a template set of macros to use is by specifying the \"-g\" (\"--global\")\noption with h2xs (see h2xs).\n\nBelow is an example module that makes use of the macros.\n\n#define PERLNOGETCONTEXT\n#include \"EXTERN.h\"\n#include \"perl.h\"\n#include \"XSUB.h\"\n\n/* Global Data */\n\n#define MYCXTKEY \"BlindMice::guts\" XSVERSION\n\ntypedef struct {\nint count;\nchar name[3][100];\n} mycxtt;\n\nSTARTMYCXT\n\nMODULE = BlindMice PACKAGE = BlindMice\n\nBOOT:\n{\nMYCXTINIT;\nMYCXT.count = 0;\nstrcpy(MYCXT.name[0], \"None\");\nstrcpy(MYCXT.name[1], \"None\");\nstrcpy(MYCXT.name[2], \"None\");\n}\n\nint\nnewMouse(char * name)\nPREINIT:\ndMYCXT;\nCODE:\nif (MYCXT.count >= 3) {\nwarn(\"Already have 3 blind mice\");\nRETVAL = 0;\n}\nelse {\nRETVAL = ++ MYCXT.count;\nstrcpy(MYCXT.name[MYCXT.count - 1], name);\n}\nOUTPUT:\nRETVAL\n\nchar *\ngetmousename(index)\nint index\nPREINIT:\ndMYCXT;\nCODE:\nif (index > MYCXT.count)\ncroak(\"There are only 3 blind mice.\");\nelse\nRETVAL = MYCXT.name[index - 1];\nOUTPUT:\nRETVAL\n\nvoid\nCLONE(...)\nCODE:\nMYCXTCLONE;\n\nMYCXT REFERENCE\nMYCXTKEY\nThis macro is used to define a unique key to refer to the static data for an XS module. The\nsuggested naming scheme, as used by h2xs, is to use a string that consists of the module\nname, the string \"::guts\" and the module version number.\n\n#define MYCXTKEY \"MyModule::guts\" XSVERSION\n\ntypedef mycxtt\nThis struct typedef *must* always be called \"mycxtt\". The other \"CXT*\" macros assume the\nexistence of the \"mycxtt\" typedef name.\n\nDeclare a typedef named \"mycxtt\" that is a structure that contains all the data that\nneeds to be interpreter-local.\n\ntypedef struct {\nint somevalue;\n} mycxtt;\n\nSTARTMYCXT\nAlways place the STARTMYCXT macro directly after the declaration of \"mycxtt\".\n\nMYCXTINIT\nThe MYCXTINIT macro initializes storage for the \"mycxtt\" struct.\n\nIt *must* be called exactly once, typically in a BOOT: section. If you are maintaining\nmultiple interpreters, it should be called once in each interpreter instance, except for\ninterpreters cloned from existing ones. (But see \"MYCXTCLONE\" below.)\n\ndMYCXT\nUse the dMYCXT macro (a declaration) in all the functions that access MYCXT.\n\nMYCXT\nUse the MYCXT macro to access members of the \"mycxtt\" struct. For example, if \"mycxtt\"\nis\n\ntypedef struct {\nint index;\n} mycxtt;\n\nthen use this to access the \"index\" member\n\ndMYCXT;\nMYCXT.index = 2;\n\naMYCXT/pMYCXT\n\"dMYCXT\" may be quite expensive to calculate, and to avoid the overhead of invoking it in\neach function it is possible to pass the declaration onto other functions using the\n\"aMYCXT\"/\"pMYCXT\" macros, eg\n\nvoid sub1() {\ndMYCXT;\nMYCXT.index = 1;\nsub2(aMYCXT);\n}\n\nvoid sub2(pMYCXT) {\nMYCXT.index = 2;\n}\n\nAnalogously to \"pTHX\", there are equivalent forms for when the macro is the first or last\nin multiple arguments, where an underscore represents a comma, i.e. \"aMYCXT\", \"aMYCXT\",\n\"pMYCXT\" and \"pMYCXT\".\n\nMYCXTCLONE\nBy default, when a new interpreter is created as a copy of an existing one (eg via\n\"threads->create()\"), both interpreters share the same physical mycxtt structure. Calling\n\"MYCXTCLONE\" (typically via the package's \"CLONE()\" function), causes a byte-for-byte\ncopy of the structure to be taken, and any future dMYCXT will cause the copy to be\naccessed instead.\n\nMYCXTINITINTERP(myperl)" }, { "name": "dMY_CXT_INTERP", "content": "These are versions of the macros which take an explicit interpreter as an argument.\n\nNote that these macros will only work together within the *same* source file; that is, a dMYCTX\nin one source file will access a different structure than a dMYCTX in another source file.\n" }, { "name": "Thread-aware system interfaces", "content": "Starting from Perl 5.8, in C/C++ level Perl knows how to wrap system/library interfaces that\nhave thread-aware versions (e.g. getpwentr()) into frontend macros (e.g. getpwent()) that\ncorrectly handle the multithreaded interaction with the Perl interpreter. This will happen\ntransparently, the only thing you need to do is to instantiate a Perl interpreter.\n\nThis wrapping happens always when compiling Perl core source (PERLCORE is defined) or the Perl\ncore extensions (PERLEXT is defined). When compiling XS code outside of the Perl core, the\nwrapping does not take place before Perl 5.28. Starting in that release you can\n\n#define PERLREENTRANT\n\nin your code to enable the wrapping. It is advisable to do so if you are using such functions,\nas intermixing the \"r\"-forms (as Perl compiled for multithreaded operation will do) and the\n\"r\"-less forms is neither well-defined (inconsistent results, data corruption, or even crashes\nbecome more likely), nor is it very portable. Unfortunately, not all systems have all the \"r\"\nforms, but using this \"#define\" gives you whatever protection that Perl is aware is available on\neach system.\n" } ] }, "EXAMPLES": { "content": "File \"RPC.xs\": Interface to some ONC+ RPC bind library functions.\n\n#define PERLNOGETCONTEXT\n#include \"EXTERN.h\"\n#include \"perl.h\"\n#include \"XSUB.h\"\n\n/* Note: On glibc 2.13 and earlier, this needs be */\n#include \n\ntypedef struct netconfig Netconfig;\n\nMODULE = RPC PACKAGE = RPC\n\nSV *\nrpcbgettime(host=\"localhost\")\nchar *host\nPREINIT:\ntimet timep;\nCODE:\nST(0) = svnewmortal();\nif( rpcbgettime( host, &timep ) )\nsvsetnv( ST(0), (double)timep );\n\nNetconfig *\ngetnetconfigent(netid=\"udp\")\nchar *netid\n\nMODULE = RPC PACKAGE = NetconfigPtr PREFIX = rpcb\n\nvoid\nrpcbDESTROY(netconf)\nNetconfig *netconf\nCODE:\nprintf(\"NetconfigPtr::DESTROY\\n\");\nfree( netconf );\n\nFile \"typemap\": Custom typemap for RPC.xs. (cf. perlxstypemap)\n\nTYPEMAP\nNetconfig * TPTROBJ\n\nFile \"RPC.pm\": Perl module for the RPC extension.\n\npackage RPC;\n\nrequire Exporter;\nrequire DynaLoader;\n@ISA = qw(Exporter DynaLoader);\n@EXPORT = qw(rpcbgettime getnetconfigent);\n\nbootstrap RPC;\n1;\n\nFile \"rpctest.pl\": Perl test program for the RPC extension.\n\nuse RPC;\n\n$netconf = getnetconfigent();\n$a = rpcbgettime();\nprint \"time = $a\\n\";\nprint \"netconf = $netconf\\n\";\n\n$netconf = getnetconfigent(\"tcp\");\n$a = rpcbgettime(\"poplar\");\nprint \"time = $a\\n\";\nprint \"netconf = $netconf\\n\";\n\nIn Makefile.PL add -ltirpc and -I/usr/include/tirpc.\n", "subsections": [] }, "CAVEATS": { "content": "XS code has full access to system calls including C library functions. It thus has the\ncapability of interfering with things that the Perl core or other modules have set up, such as\nsignal handlers or file handles. It could mess with the memory, or any number of harmful things.\nDon't.\n\nSome modules have an event loop, waiting for user-input. It is highly unlikely that two such\nmodules would work adequately together in a single Perl application.\n\nIn general, the perl interpreter views itself as the center of the universe as far as the Perl\nprogram goes. XS code is viewed as a help-mate, to accomplish things that perl doesn't do, or\ndoesn't do fast enough, but always subservient to perl. The closer XS code adheres to this\nmodel, the less likely conflicts will occur.\n\nOne area where there has been conflict is in regards to C locales. (See perllocale.) perl, with\none exception and unless told otherwise, sets up the underlying locale the program is running in\nto the locale passed into it from the environment. This is an important difference from a\ngeneric C language program, where the underlying locale is the \"C\" locale unless the program\nchanges it. As of v5.20, this underlying locale is completely hidden from pure Perl code outside\nthe lexical scope of \"use locale\" except for a couple of function calls in the POSIX module\nwhich of necessity use it. But the underlying locale, with that one exception is exposed to XS\ncode, affecting all C library routines whose behavior is locale-dependent. Your XS code better\nnot assume that the underlying locale is \"C\". The exception is the \"LCNUMERIC\" locale category,\nand the reason it is an exception is that experience has shown that it can be problematic for XS\ncode, whereas we have not had reports of problems with the other locale categories. And the\nreason for this one category being problematic is that the character used as a decimal point can\nvary. Many European languages use a comma, whereas English, and hence Perl are expecting a dot\n(U+002E: FULL STOP). Many modules can handle only the radix character being a dot, and so perl\nattempts to make it so. Up through Perl v5.20, the attempt was merely to set \"LCNUMERIC\" upon\nstartup to the \"C\" locale. Any setlocale() otherwise would change it; this caused some failures.\nTherefore, starting in v5.22, perl tries to keep \"LCNUMERIC\" always set to \"C\" for XS code.\n\nTo summarize, here's what to expect and how to handle locales in XS code:\n\nNon-locale-aware XS code\nKeep in mind that even if you think your code is not locale-aware, it may call a library\nfunction that is. Hopefully the man page for such a function will indicate that dependency,\nbut the documentation is imperfect.\n\nThe current locale is exposed to XS code except possibly \"LCNUMERIC\" (explained in the next\nparagraph). There have not been reports of problems with the other categories. Perl\ninitializes things on start-up so that the current locale is the one which is indicated by\nthe user's environment in effect at that time. See \"ENVIRONMENT\" in perllocale.\n\nHowever, up through v5.20, Perl initialized things on start-up so that \"LCNUMERIC\" was set\nto the \"C\" locale. But if any code anywhere changed it, it would stay changed. This means\nthat your module can't count on \"LCNUMERIC\" being something in particular, and you can't\nexpect floating point numbers (including version strings) to have dots in them. If you don't\nallow for a non-dot, your code could break if anyone anywhere changed the locale. For this\nreason, v5.22 changed the behavior so that Perl tries to keep \"LCNUMERIC\" in the \"C\" locale\nexcept around the operations internally where it should be something else. Misbehaving XS\ncode will always be able to change the locale anyway, but the most common instance of this\nis checked for and handled.\n\nLocale-aware XS code\nIf the locale from the user's environment is desired, there should be no need for XS code to\nset the locale except for \"LCNUMERIC\", as perl has already set the others up. XS code\nshould avoid changing the locale, as it can adversely affect other, unrelated, code and may\nnot be thread-safe. To minimize problems, the macros \"STORELCNUMERICSETTONEEDED\" in\nperlapi, \"STORELCNUMERICFORCETOUNDERLYING\" in perlapi, and \"RESTORELCNUMERIC\" in\nperlapi should be used to affect any needed change.\n\nBut, starting with Perl v5.28, locales are thread-safe on platforms that support this\nfunctionality. Windows has this starting with Visual Studio 2005. Many other modern\nplatforms support the thread-safe POSIX 2008 functions. The C \"#define\"\n\"USETHREADSAFELOCALE\" will be defined iff this build is using these. From Perl-space, the\nread-only variable \"${SAFELOCALES}\" is 1 if either the build is not threaded, or if\n\"USETHREADSAFELOCALE\" is defined; otherwise it is 0.\n\nThe way this works under-the-hood is that every thread has a choice of using a locale\nspecific to it (this is the Windows and POSIX 2008 functionality), or the global locale that\nis accessible to all threads (this is the functionality that has always been there). The\nimplementations for Windows and POSIX are completely different. On Windows, the runtime can\nbe set up so that the standard setlocale(3) function either only knows about the global\nlocale or the locale for this thread. On POSIX, \"setlocale\" always deals with the global\nlocale, and other functions have been created to handle per-thread locales. Perl makes this\ntransparent to perl-space code. It continues to use \"POSIX::setlocale()\", and the\ninterpreter translates that into the per-thread functions.\n\nAll other locale-sensitive functions automatically use the per-thread locale, if that is\nturned on, and failing that, the global locale. Thus calls to \"setlocale\" are ineffective on\nPOSIX systems for the current thread if that thread is using a per-thread locale. If perl is\ncompiled for single-thread operation, it does not use the per-thread functions, so\n\"setlocale\" does work as expected.\n\nIf you have loaded the \"POSIX\" module you can use the methods given in perlcall to call\n\"POSIX::setlocale\" to safely change or query the locale (on systems where it is safe to do\nso), or you can use the new 5.28 function \"Perlsetlocale\" in perlapi instead, which is a\ndrop-in replacement for the system setlocale(3), and handles single-threaded and\nmulti-threaded applications transparently.\n\nThere are some locale-related library calls that still aren't thread-safe because they\nreturn data in a buffer global to all threads. In the past, these didn't matter as locales\nweren't thread-safe at all. But now you have to be aware of them in case your module is\ncalled in a multi-threaded application. The known ones are\n\nasctime()\nctime()\ngcvt() [POSIX.1-2001 only (function removed in POSIX.1-2008)]\ngetdate()\nwcrtomb() if its final argument is NULL\nwcsrtombs() if its final argument is NULL\nwcstombs()\nwctomb()\n\nSome of these shouldn't really be called in a Perl application, and for others there are\nthread-safe versions of these already implemented:\n\nasctimer()\nctimer()\nPerllanginfo()\n\nThe \"r\" forms are automatically used, starting in Perl 5.28, if you compile your code, with\n\n#define PERLREENTRANT\n\nSee also \"Perllanginfo\" in perlapi. You can use the methods given in perlcall, to get the\nbest available locale-safe versions of these\n\nPOSIX::localeconv()\nPOSIX::wcstombs()\nPOSIX::wctomb()\n\nAnd note, that some items returned by \"Localeconv\" are available through \"Perllanginfo\" in\nperlapi.\n\nThe others shouldn't be used in a threaded application.\n\nSome modules may call a non-perl library that is locale-aware. This is fine as long as it\ndoesn't try to query or change the locale using the system \"setlocale\". But if these do call\nthe system \"setlocale\", those calls may be ineffective. Instead, \"Perlsetlocale\" works in\nall circumstances. Plain setlocale is ineffective on multi-threaded POSIX 2008 systems. It\noperates only on the global locale, whereas each thread has its own locale, paying no\nattention to the global one. Since converting these non-Perl libraries to \"Perlsetlocale\"\nis out of the question, there is a new function in v5.28 \"switchtogloballocale\" that will\nswitch the thread it is called from so that any system \"setlocale\" calls will have their\ndesired effect. The function \"synclocale\" must be called before returning to perl.\n\nThis thread can change the locale all it wants and it won't affect any other thread, except\nany that also have been switched to the global locale. This means that a multi-threaded\napplication can have a single thread using an alien library without a problem; but no more\nthan a single thread can be so-occupied. Bad results likely will happen.\n\nIn perls without multi-thread locale support, some alien libraries, such as \"Gtk\" change\nlocales. This can cause problems for the Perl core and other modules. For these, before\ncontrol is returned to perl, starting in v5.20.1, calling the function synclocale() from XS\nshould be sufficient to avoid most of these problems. Prior to this, you need a pure Perl\nstatement that does this:\n\nPOSIX::setlocale(LCALL, POSIX::setlocale(LCALL));\n\nor use the methods given in perlcall.\n", "subsections": [] }, "XS VERSION": { "content": "This document covers features supported by \"ExtUtils::ParseXS\" (also known as \"xsubpp\") 3.1301.\n", "subsections": [] }, "AUTHOR": { "content": "Originally written by Dean Roehrich .\n\nMaintained since 1996 by The Perl Porters .\n", "subsections": [] } } } }