X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlintern.pod;h=67ff429af01d51319de563623b65b7898039cc3b;hb=d77cdebfaf0c7eb784a132b575c93953a56db215;hp=b9bf0545b25879635ee654f304d27d0cd18ea1df;hpb=d7f8936a2fe7fc93635b0b501d1f941d30d3399f;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perlintern.pod b/pod/perlintern.pod index b9bf054..67ff429 100644 --- a/pod/perlintern.pod +++ b/pod/perlintern.pod @@ -1,9 +1,16 @@ +-*- buffer-read-only: t -*- + +!!!!!!! DO NOT EDIT THIS FILE !!!!!!! +This file is built by autodoc.pl extracting documentation from the C source +files. + =head1 NAME perlintern - autogenerated documentation of purely B Perl functions =head1 DESCRIPTION +X X This file is the autogenerated documentation of functions in the Perl interpreter that are documented using Perl's internal documentation @@ -16,6 +23,7 @@ B! =over 8 =item CvWEAKOUTSIDE +X Each CV has a pointer, C, to its lexically enclosing CV (if any). Because pointers to anonymous sub prototypes are @@ -78,6 +86,7 @@ Found in file cv.h =over 8 =item CX_CURPAD_SAVE +X Save the current pad in the given context block structure. @@ -87,6 +96,7 @@ Save the current pad in the given context block structure. Found in file pad.h =item CX_CURPAD_SV +X Access the SV at offset po in the saved current pad in the given context block structure (can be used as an lvalue). @@ -96,26 +106,28 @@ context block structure (can be used as an lvalue). =for hackers Found in file pad.h -=item PAD_BASE_SV +=item PAD_BASE_SV +X Get the value from slot C in the base (DEPTH=1) pad of a padlist - SV * PAD_BASE_SV (PADLIST padlist, PADOFFSET po) + SV * PAD_BASE_SV(PADLIST padlist, PADOFFSET po) =for hackers Found in file pad.h =item PAD_CLONE_VARS +X -|CLONE_PARAMS* param Clone the state variables associated with running and compiling pads. - void PAD_CLONE_VARS(PerlInterpreter *proto_perl \) + void PAD_CLONE_VARS(PerlInterpreter *proto_perl, CLONE_PARAMS* param) =for hackers Found in file pad.h =item PAD_COMPNAME_FLAGS +X Return the flags for the current compiling pad name at offset C. Assumes a valid slot entry. @@ -126,9 +138,10 @@ at offset C. Assumes a valid slot entry. Found in file pad.h =item PAD_COMPNAME_GEN +X The generation number of the name at offset C in the current -compiling pad (lvalue). Note that C is hijacked for this purpose. +compiling pad (lvalue). Note that C is hijacked for this purpose. STRLEN PAD_COMPNAME_GEN(PADOFFSET po) @@ -136,9 +149,10 @@ compiling pad (lvalue). Note that C is hijacked for this purpose. Found in file pad.h =item PAD_COMPNAME_GEN_set +X Sets the generation number of the name at offset C in the current -ling pad (lvalue) to C. Note that C is hijacked for this purpose. +ling pad (lvalue) to C. Note that C is hijacked for this purpose. STRLEN PAD_COMPNAME_GEN_set(PADOFFSET po, int gen) @@ -146,6 +160,7 @@ ling pad (lvalue) to C. Note that C is hijacked for this purpos Found in file pad.h =item PAD_COMPNAME_OURSTASH +X Return the stash associated with an C variable. Assumes the slot entry is a valid C lexical. @@ -156,6 +171,7 @@ Assumes the slot entry is a valid C lexical. Found in file pad.h =item PAD_COMPNAME_PV +X Return the name of the current compiling pad name at offset C. Assumes a valid slot entry. @@ -166,6 +182,7 @@ at offset C. Assumes a valid slot entry. Found in file pad.h =item PAD_COMPNAME_TYPE +X Return the type (stash) of the current compiling pad name at offset C. Must be a valid name. Returns null if not typed. @@ -176,6 +193,7 @@ C. Must be a valid name. Returns null if not typed. Found in file pad.h =item PAD_DUP +X Clone a padlist. @@ -185,6 +203,7 @@ Clone a padlist. Found in file pad.h =item PAD_RESTORE_LOCAL +X Restore the old pad saved into the local variable opad by PAD_SAVE_LOCAL() @@ -194,6 +213,7 @@ Restore the old pad saved into the local variable opad by PAD_SAVE_LOCAL() Found in file pad.h =item PAD_SAVE_LOCAL +X Save the current pad to the local variable opad, then make the current pad equal to npad @@ -204,6 +224,7 @@ current pad equal to npad Found in file pad.h =item PAD_SAVE_SETNULLPAD +X Save the current pad then set it to null. @@ -212,16 +233,18 @@ Save the current pad then set it to null. =for hackers Found in file pad.h -=item PAD_SETSV +=item PAD_SETSV +X Set the slot at offset C in the current pad to C - SV * PAD_SETSV (PADOFFSET po, SV* sv) + SV * PAD_SETSV(PADOFFSET po, SV* sv) =for hackers Found in file pad.h -=item PAD_SET_CUR +=item PAD_SET_CUR +X Set the current pad to be pad C in the padlist, saving the previous current pad. NB currently this macro expands to a string too @@ -231,51 +254,56 @@ long for some compilers, so it's best to replace it with PAD_SET_CUR_NOSAVE(padlist,n); - void PAD_SET_CUR (PADLIST padlist, I32 n) + void PAD_SET_CUR(PADLIST padlist, I32 n) =for hackers Found in file pad.h -=item PAD_SET_CUR_NOSAVE +=item PAD_SET_CUR_NOSAVE +X like PAD_SET_CUR, but without the save - void PAD_SET_CUR_NOSAVE (PADLIST padlist, I32 n) + void PAD_SET_CUR_NOSAVE(PADLIST padlist, I32 n) =for hackers Found in file pad.h -=item PAD_SV +=item PAD_SV +X Get the value at offset C in the current pad - void PAD_SV (PADOFFSET po) + void PAD_SV(PADOFFSET po) =for hackers Found in file pad.h -=item PAD_SVl +=item PAD_SVl +X Lightweight and lvalue version of C. Get or set the value at offset C in the current pad. Unlike C, does not print diagnostics with -DX. For internal use only. - SV * PAD_SVl (PADOFFSET po) + SV * PAD_SVl(PADOFFSET po) =for hackers Found in file pad.h -=item SAVECLEARSV +=item SAVECLEARSV +X Clear the pointed to pad value on scope exit. (i.e. the runtime action of 'my') - void SAVECLEARSV (SV **svp) + void SAVECLEARSV(SV **svp) =for hackers Found in file pad.h =item SAVECOMPPAD +X save PL_comppad and PL_curpad @@ -288,12 +316,13 @@ save PL_comppad and PL_curpad =for hackers Found in file pad.h -=item SAVEPADSV +=item SAVEPADSV +X Save a pad slot (used to restore after an iteration) XXX DAPM it would make more sense to make the arg a PADOFFSET - void SAVEPADSV (PADOFFSET po) + void SAVEPADSV(PADOFFSET po) =for hackers Found in file pad.h @@ -301,174 +330,188 @@ Found in file pad.h =back -=head1 Functions in file pp_ctl.c - +=head1 GV Functions =over 8 -=item find_runcv - -Locate the CV corresponding to the currently executing sub or eval. -If db_seqp is non_null, skip CVs that are in the DB package and populate -*db_seqp with the cop sequence number at the point that the DB:: code was -entered. (allows debuggers to eval in the scope of the breakpoint rather -than in in the scope of the debugger itself). +=item is_gv_magical +X - CV* find_runcv(U32 *db_seqp) +Returns C if given the name of a magical GV. -=for hackers -Found in file pp_ctl.c +Currently only useful internally when determining if a GV should be +created even in rvalue contexts. +C is not used at present but available for future extension to +allow selecting particular classes of magical variable. -=back +Currently assumes that C is NUL terminated (as well as len being valid). +This assumption is met by all callers within the perl core, which all pass +pointers returned by SvPV. -=head1 Global Variables + bool is_gv_magical(const char *name, STRLEN len, U32 flags) -=over 8 +=for hackers +Found in file gv.c -=item PL_DBsingle +=item is_gv_magical_sv +X -When Perl is run in debugging mode, with the B<-d> switch, this SV is a -boolean which indicates whether subs are being single-stepped. -Single-stepping is automatically turned on after every step. This is the C -variable which corresponds to Perl's $DB::single variable. See -C. +Returns C if given the name of a magical GV. Calls is_gv_magical. - SV * PL_DBsingle + bool is_gv_magical_sv(SV *name, U32 flags) =for hackers -Found in file intrpvar.h +Found in file gv.c -=item PL_DBsub -When Perl is run in debugging mode, with the B<-d> switch, this GV contains -the SV which holds the name of the sub being debugged. This is the C -variable which corresponds to Perl's $DB::sub variable. See -C. +=back - GV * PL_DBsub +=head1 Hash Manipulation Functions -=for hackers -Found in file intrpvar.h +=over 8 -=item PL_DBtrace +=item refcounted_he_chain_2hv +X -Trace variable used when Perl is run in debugging mode, with the B<-d> -switch. This is the C variable which corresponds to Perl's $DB::trace -variable. See C. +Generates and returns a C by walking up the tree starting at the passed +in C. - SV * PL_DBtrace + HV * refcounted_he_chain_2hv(const struct refcounted_he *c) =for hackers -Found in file intrpvar.h +Found in file hv.c -=item PL_dowarn +=item refcounted_he_free +X -The C variable which corresponds to Perl's $^W warning variable. +Decrements the reference count of the passed in C +by one. If the reference count reaches zero the structure's memory is freed, +and C iterates onto the parent node. - bool PL_dowarn + void refcounted_he_free(struct refcounted_he *he) =for hackers -Found in file intrpvar.h +Found in file hv.c -=item PL_last_in_gv +=item refcounted_he_new +X -The GV which was last used for a filehandle input operation. (C<< >>) +Creates a new C. As S is copied, and value is +stored in a compact form, all references remain the property of the caller. +The C is returned with a reference count of 1. - GV* PL_last_in_gv + struct refcounted_he * refcounted_he_new(struct refcounted_he *const parent, SV *const key, SV *const value) =for hackers -Found in file thrdvar.h +Found in file hv.c -=item PL_ofs_sv -The output field separator - C<$,> in Perl space. +=back - SV* PL_ofs_sv +=head1 IO Functions -=for hackers -Found in file thrdvar.h +=over 8 -=item PL_rs +=item start_glob +X -The input record separator - C<$/> in Perl space. +Function called by C to spawn a glob (or do the glob inside +perl on VMS). This code used to be inline, but now perl uses C +this glob starter is only used by miniperl during the build process. +Moving it away shrinks pp_hot.c; shrinking pp_hot.c helps speed perl up. - SV* PL_rs + PerlIO* start_glob(SV* pattern, IO *io) =for hackers -Found in file thrdvar.h +Found in file doio.c =back -=head1 GV Functions +=head1 Magical Functions =over 8 -=item is_gv_magical - -Returns C if given the name of a magical GV. - -Currently only useful internally when determining if a GV should be -created even in rvalue contexts. +=item magic_sethint +X -C is not used at present but available for future extension to -allow selecting particular classes of magical variable. +Triggered by a delete from %^H, records the key to +C. -Currently assumes that C is NUL terminated (as well as len being valid). -This assumption is met by all callers within the perl core, which all pass -pointers returned by SvPV. - - bool is_gv_magical(const char *name, STRLEN len, U32 flags) + int magic_sethint(SV* sv, MAGIC* mg) =for hackers -Found in file gv.c +Found in file mg.c -=item is_gv_magical_sv +=item mg_localize +X -Returns C if given the name of a magical GV. Calls is_gv_magical. +Copy some of the magic from an existing SV to new localized version of +that SV. Container magic (eg %ENV, $1, tie) gets copied, value magic +doesn't (eg taint, pos). - bool is_gv_magical_sv(SV *name, U32 flags) + void mg_localize(SV* sv, SV* nsv) =for hackers -Found in file gv.c +Found in file mg.c =back -=head1 IO Functions +=head1 MRO Functions =over 8 -=item start_glob +=item mro_get_linear_isa_c3 +X -Function called by C to spawn a glob (or do the glob inside -perl on VMS). This code used to be inline, but now perl uses C -this glob starter is only used by miniperl during the build process. -Moving it away shrinks pp_hot.c; shrinking pp_hot.c helps speed perl up. +Returns the C3 linearization of @ISA +the given stash. The return value is a read-only AV*. +C should be 0 (it is used internally in this +function's recursion). - PerlIO* start_glob(SV* pattern, IO *io) +You are responsible for C on the +return value if you plan to store it anywhere +semi-permanently (otherwise it might be deleted +out from under you the next time the cache is +invalidated). + + AV* mro_get_linear_isa_c3(HV* stash, I32 level) =for hackers -Found in file doio.c +Found in file mro.c +=item mro_get_linear_isa_dfs +X -=back +Returns the Depth-First Search linearization of @ISA +the given stash. The return value is a read-only AV*. +C should be 0 (it is used internally in this +function's recursion). -=head1 Magical Functions +You are responsible for C on the +return value if you plan to store it anywhere +semi-permanently (otherwise it might be deleted +out from under you the next time the cache is +invalidated). -=over 8 + AV* mro_get_linear_isa_dfs(HV* stash, I32 level) -=item mg_localize +=for hackers +Found in file mro.c -Copy some of the magic from an existing SV to new localized version of -that SV. Container magic (eg %ENV, $1, tie) gets copied, value magic -doesn't (eg taint, pos). +=item mro_isa_changed_in +X - void mg_localize(SV* sv, SV* nsv) +Takes the necessary steps (cache invalidations, mostly) +when the @ISA of the given package has changed. Invoked +by the C magic, should not need to invoke directly. + + void mro_isa_changed_in(HV* stash) =for hackers -Found in file mg.c +Found in file mro.c =back @@ -478,6 +521,7 @@ Found in file mg.c =over 8 =item CvPADLIST +X CV's can have CvPADLIST(cv) set to point to an AV. @@ -523,19 +567,19 @@ but only by their index allocated at compile time (which is usually in PL_op->op_targ), wasting a name SV for them doesn't make sense. The SVs in the names AV have their PV being the name of the variable. -NV+1..IV inclusive is a range of cop_seq numbers for which the name is -valid. For typed lexicals name SV is SVt_PVMG and SvSTASH points at the -type. For C lexicals, the type is SVt_PVGV, and GvSTASH points at the -stash of the associated global (so that duplicate C declarations in the -same package can be detected). SvCUR is sometimes hijacked to -store the generation number during compilation. +xlow+1..xhigh inclusive in the NV union is a range of cop_seq numbers for +which the name is valid. For typed lexicals name SV is SVt_PVMG and SvSTASH +points at the type. For C lexicals, the type is also SVt_PVMG, with the +SvOURSTASH slot pointing at the stash of the associated global (so that +duplicate C declarations in the same package can be detected). SvUVX is +sometimes hijacked to store the generation number during compilation. If SvFAKE is set on the name SV, then that slot in the frame AV is a REFCNT'ed reference to a lexical from "outside". In this case, -the name SV does not use NVX and IVX to store a cop_seq range, since it is -in scope throughout. Instead IVX stores some flags containing info about +the name SV does not use xlow and xhigh to store a cop_seq range, since it is +in scope throughout. Instead xhigh stores some flags containing info about the real lexical (is it declared in an anon, and is it capable of being -instantiated multiple times?), and for fake ANONs, NVX contains the index +instantiated multiple times?), and for fake ANONs, xlow contains the index within the parent's pad where the lexical's value is stored, to make cloning quicker. @@ -559,6 +603,7 @@ to be generated in evals, such as Found in file pad.c =item cv_clone +X Clone a CV: make a new CV which points to the same code etc, but which has a newly-created pad built by copying the prototype pad and capturing @@ -570,6 +615,7 @@ any outer lexicals. Found in file pad.c =item cv_dump +X dump the contents of a CV @@ -579,6 +625,7 @@ dump the contents of a CV Found in file pad.c =item do_dump_pad +X Dump the contents of a padlist @@ -588,6 +635,7 @@ Dump the contents of a padlist Found in file pad.c =item intro_my +X "Introduce" my variables to visible status. @@ -597,6 +645,7 @@ Found in file pad.c Found in file pad.c =item pad_add_anon +X Add an anon code entry to the current compiling pad @@ -606,26 +655,28 @@ Add an anon code entry to the current compiling pad Found in file pad.c =item pad_add_name +X Create a new name and associated PADMY SV in the current pad; return the offset. If C is valid, the name is for a typed lexical; set the name's stash to that value. If C is valid, it's an our lexical, set the name's -GvSTASH to that value +SvOURSTASH to that value If fake, it means we're cloning an existing entry - PADOFFSET pad_add_name(const char *name, HV* typestash, HV* ourstash, bool clone) + PADOFFSET pad_add_name(const char *name, HV* typestash, HV* ourstash, bool clone, bool state) =for hackers Found in file pad.c =item pad_alloc +X Allocate a new my or tmp pad entry. For a my, simply push a null SV onto the end of PL_comppad, but for a tmp, scan the pad from PL_padix upwards -for a slot which has no name and and no active value. +for a slot which has no name and no active value. PADOFFSET pad_alloc(I32 optype, U32 tmptype) @@ -633,6 +684,7 @@ for a slot which has no name and and no active value. Found in file pad.c =item pad_block_start +X Update the pad compilation state variables on entry to a new block @@ -642,6 +694,7 @@ Update the pad compilation state variables on entry to a new block Found in file pad.c =item pad_check_dup +X Check for duplicate declarations: report any of: * a my in the current scope with the same name; @@ -655,6 +708,7 @@ C indicates that the name to check is an 'our' declaration Found in file pad.c =item pad_findlex +X Find a named lexical anywhere in a chain of nested pads. Add fake entries in the inner pads if it's found in an outer one. @@ -670,7 +724,7 @@ associated with the IVX field of a fake namesv. Note that pad_findlex() is recursive; it recurses up the chain of CVs, then comes back down, adding fake entries as it goes. It has to be this way -because fake namesvs in anon protoypes have to store in NVX the index into +because fake namesvs in anon protoypes have to store in xlow the index into the parent pad. PADOFFSET pad_findlex(const char *name, const CV* cv, U32 seq, int warn, SV** out_capture, SV** out_name_sv, int *out_flags) @@ -679,6 +733,7 @@ the parent pad. Found in file pad.c =item pad_findmy +X Given a lexical name, try to find its offset, first in the current pad, or failing that, in the pads of any lexically enclosing subs (including @@ -692,6 +747,7 @@ Returns the offset in the current pad, or NOT_IN_PAD on failure. Found in file pad.c =item pad_fixup_inner_anons +X For any anon CVs in the pad, change CvOUTSIDE of that CV from old_cv to new_cv if necessary. Needed when a newly-compiled CV has to be @@ -703,6 +759,7 @@ moved to a pre-existing CV struct. Found in file pad.c =item pad_free +X Free the SV at offset po in the current pad. @@ -712,6 +769,7 @@ Free the SV at offset po in the current pad. Found in file pad.c =item pad_leavemy +X Cleanup at end of scope during compilation: set the max seq number for lexicals in this scope and warn of any lexicals that never got introduced. @@ -722,6 +780,7 @@ lexicals in this scope and warn of any lexicals that never got introduced. Found in file pad.c =item pad_new +X Create a new compiling padlist, saving and updating the various global vars at the same time as creating the pad itself. The following flags @@ -737,6 +796,7 @@ can be OR'ed together: Found in file pad.c =item pad_push +X Push a new pad frame onto the padlist, unless there's already a pad at this depth, in which case don't bother creating a new one. Then give @@ -748,6 +808,7 @@ the new pad an @_ in slot zero. Found in file pad.c =item pad_reset +X Mark all the current temporaries for reuse @@ -757,6 +818,7 @@ Mark all the current temporaries for reuse Found in file pad.c =item pad_setsv +X Set the entry at offset po in the current pad to sv. Use the macro PAD_SETSV() rather than calling this function directly. @@ -767,6 +829,7 @@ Use the macro PAD_SETSV() rather than calling this function directly. Found in file pad.c =item pad_swipe +X Abandon the tmp in the current pad at offset po and replace with a new one. @@ -777,6 +840,7 @@ new one. Found in file pad.c =item pad_tidy +X Tidy up a pad after we've finished compiling it: * remove most stuff from the pads of anonsub prototypes; @@ -789,6 +853,7 @@ Tidy up a pad after we've finished compiling it: Found in file pad.c =item pad_undef +X Free the padlist associated with a CV. If parts of it happen to be current, we null the relevant @@ -807,11 +872,98 @@ Found in file pad.c =back +=head1 Per-Interpreter Variables + +=over 8 + +=item PL_DBsingle +X + +When Perl is run in debugging mode, with the B<-d> switch, this SV is a +boolean which indicates whether subs are being single-stepped. +Single-stepping is automatically turned on after every step. This is the C +variable which corresponds to Perl's $DB::single variable. See +C. + + SV * PL_DBsingle + +=for hackers +Found in file intrpvar.h + +=item PL_DBsub +X + +When Perl is run in debugging mode, with the B<-d> switch, this GV contains +the SV which holds the name of the sub being debugged. This is the C +variable which corresponds to Perl's $DB::sub variable. See +C. + + GV * PL_DBsub + +=for hackers +Found in file intrpvar.h + +=item PL_DBtrace +X + +Trace variable used when Perl is run in debugging mode, with the B<-d> +switch. This is the C variable which corresponds to Perl's $DB::trace +variable. See C. + + SV * PL_DBtrace + +=for hackers +Found in file intrpvar.h + +=item PL_dowarn +X + +The C variable which corresponds to Perl's $^W warning variable. + + bool PL_dowarn + +=for hackers +Found in file intrpvar.h + +=item PL_last_in_gv +X + +The GV which was last used for a filehandle input operation. (C<< >>) + + GV* PL_last_in_gv + +=for hackers +Found in file intrpvar.h + +=item PL_ofs_sv +X + +The output field separator - C<$,> in Perl space. + + SV* PL_ofs_sv + +=for hackers +Found in file intrpvar.h + +=item PL_rs +X + +The input record separator - C<$/> in Perl space. + + SV* PL_rs + +=for hackers +Found in file intrpvar.h + + +=back + =head1 Stack Manipulation Macros =over 8 =item djSP +X Declare Just C. This is actually identical to C, and declares a local copy of perl's stack pointer, available via the C macro. @@ -824,6 +976,7 @@ old (Perl 5.005) thread model.) Found in file pp.h =item LVRET +X True if this op will be the return value of an lvalue subroutine @@ -837,37 +990,8 @@ Found in file pp.h =over 8 -=item find_uninit_var - -Find the name of the undefined variable (if any) that caused the operator o -to issue a "Use of uninitialized value" warning. -If match is true, only return a name if it's value matches uninit_sv. -So roughly speaking, if a unary operator (such as OP_COS) generates a -warning, then following the direct child of the op may yield an -OP_PADSV or OP_GV that gives the name of the undefined variable. On the -other hand, with OP_ADD there are two branches to follow, so we only print -the variable name if we get an exact match. - -The name is returned as a mortal SV. - -Assumes that PL_op is the op that originally triggered the error, and that -PL_comppad/PL_curpad points to the currently executing pad. - - SV* find_uninit_var(OP* obase, SV* uninit_sv, bool top) - -=for hackers -Found in file sv.c - -=item report_uninit - -Print appropriate "Use of uninitialized variable" warning - - void report_uninit(SV* uninit_sv) - -=for hackers -Found in file sv.c - =item sv_add_arena +X Given a chunk of memory, link it to the head of the list of arenas, and split it into a list of free SVs. @@ -878,6 +1002,7 @@ and split it into a list of free SVs. Found in file sv.c =item sv_clean_all +X Decrement the refcnt of each remaining SV, possibly triggering a cleanup. This function may have to be called multiple times to free @@ -889,6 +1014,7 @@ SVs which are in complex self-referential hierarchies. Found in file sv.c =item sv_clean_objs +X Attempt to destroy all objects not yet freed @@ -898,6 +1024,7 @@ Attempt to destroy all objects not yet freed Found in file sv.c =item sv_free_arenas +X Deallocate the memory used by all arenas. Note that all the individual SV heads and bodies within the arenas must already have been freed. @@ -910,6 +1037,64 @@ Found in file sv.c =back +=head1 SV-Body Allocation + +=over 8 + +=item sv_2num +X + +Return an SV with the numeric value of the source SV, doing any necessary +reference or overload conversion. You must use the C macro to +access this function. + + SV* sv_2num(SV* sv) + +=for hackers +Found in file sv.c + + +=back + +=head1 Unicode Support + +=over 8 + +=item find_uninit_var +X + +Find the name of the undefined variable (if any) that caused the operator o +to issue a "Use of uninitialized value" warning. +If match is true, only return a name if it's value matches uninit_sv. +So roughly speaking, if a unary operator (such as OP_COS) generates a +warning, then following the direct child of the op may yield an +OP_PADSV or OP_GV that gives the name of the undefined variable. On the +other hand, with OP_ADD there are two branches to follow, so we only print +the variable name if we get an exact match. + +The name is returned as a mortal SV. + +Assumes that PL_op is the op that originally triggered the error, and that +PL_comppad/PL_curpad points to the currently executing pad. + + SV* find_uninit_var(OP* obase, SV* uninit_sv, bool top) + +=for hackers +Found in file sv.c + +=item report_uninit +X + +Print appropriate "Use of uninitialized variable" warning + + void report_uninit(SV* uninit_sv) + +=for hackers +Found in file sv.c + + +=back + =head1 AUTHORS The autodocumentation system was originally added to the Perl core by @@ -920,3 +1105,6 @@ document their functions. perlguts(1), perlapi(1) +=cut + + ex: set ro: