comment on

Thanks LanX for the effort and answers! I am very grateful.

To understand something you need to create a conceptual model of it. I have realized that my model of Perl and the perl interpreter was not adequate.

By following your advice to deparse the generated code, I have start to understand what is going on. I have also read some introductions to the perl interpreter.

To know the use of the

Value Stack
This stack stores the values that regular perl code is operating on, usually intermediate values of expressions within a statement. The stack itself is formed of an array of SV pointers.

for the transfer of parameters to and return values from subroutines, helps me to build my model.

In reply to Re^4: Split does not behave like a subroutine (inconsistent perldocs) by bojinlund
in thread Split does not behave like a subroutine by bojinlund

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


We don't bite newbies here... much
	PerlMonks