in reply to symbols, scope, and mod_perl

Found: manipulations on the symbols under mod_perl are visible to all threads, therefore the pointer mess I am seeing. I should manipulate the thread main function scratchpad, instead of the symbol table, but I do not know how to achieve such a thing.

Replies are listed 'Best First'.
Re^2: symbols, scope, and mod_perl
by Anonymous Monk on Oct 01, 2012 at 10:52 UTC

    Um, that sounds "fishy" :)

    Each thread gets its own symbol table, they don't share

[reply]
      Furthermore each script running under registry gets its own namespace, ex 
      ModPerl::ROOT::ModPerl::Registry::D_3a_ro_sham_bo_theEXAMPLEXPORTERtes
+t::my_dirt_sneaky_object_reference

      [download]
[reply]
[d/l]
        You are right. To be more precise, I am actually allocating the object on thread symbol table, but under mod_perl objects in "main" threads functions are persistent between calls. So it gets messed on subsequent calls. To avoid this it is needed to use a lexical variable, that does not allocate on the symbol table. To achieve the same behavior as per cgi environment, I should manipulate what it is called "stack scratchpad", but I do not have such skills.
[reply]

In Section Seekers of Perl Wisdom