Searched refs:localizing (Results 1 – 13 of 13) sorted by relevance
4353 const bool localizing = PL_op->op_private & OPpLVAL_INTRO; in PP() local4362 if (localizing) { in PP()4392 if (localizing) { in PP()4605 const bool localizing = PL_op->op_private & OPpLVAL_INTRO; in PP() local4610 if (UNLIKELY(localizing)) { in PP()4644 if (UNLIKELY(localizing)) { in PP()4803 if (UNLIKELY(localizing)) { in PP()4835 if (localizing) { in PP()6581 const bool localizing = PL_op->op_private & OPpLVAL_INTRO; in PP() local6595 if (UNLIKELY(localizing)) { in PP()[all …]
5276 if (localizing) { in PP()5283 if (lval && localizing) { in PP()5300 if (localizing && can_preserve) { in PP()5312 if (localizing) { in PP()5798 const bool localizing = PL_op->op_private & OPpLVAL_INTRO; in PP() local5801 if (localizing) { in PP()5815 if (localizing && can_preserve) { in PP()5830 if (localizing) { in PP()7493 const bool localizing = PL_op->op_private & OPpLVAL_INTRO; variable7496 if (UNLIKELY(localizing)) {[all …]
133 PERLVAR(I, localizing, U8) /* are we processing a local() list?
153 localizing
25 localizing software interfaces -- i.e., making them work in the user's462 noun should use. But suppose that you discover, while localizing an
979 but since you anticipate localizing this, you write:1285 (You may, in fact, want to start with localizing to I<one> other language
768 you can get a similar effect by localizing the corresponding array
1983 C<set> magic on localizing/assigning to a magic variable will now only
1612 Why? Because C<nasty_break()> modifies C<$\> without localizing it
1951 similar localizing behaviours. So later code blocks within the same
71 …u'll have to do that on your own. Localizing $. has the effect of also localizing Perl's notion of…
229 has the effect of also localizing Perl's notion of "the last read
115 Why? Because nasty_break() modifies C<$_> without localizing it