Re: Re^2: Grabbing Variable Names

I stand corrected. Though, actualy, I think people use the term "bytecode" somwhat incorrectly (and I say only somewhat) because the B::* tree is named B-for-Bytecode (OK, it's actualy not, it's B-for-Backend, but I think it's confusingly similar), and it's original purpose was that ineffective hack.

In any case, do you have a better term then bytecode, other then "opcode tree", which seems a little unwieldy?

Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

Comment on Re: Re^2: Grabbing Variable Names

Replies are listed 'Best First'.
Re^4: Grabbing Variable Names by diotalevi (Canon) on Jan 12, 2003 at 16:32 UTC
The B:: tree is also named after it's author, Malcolm Beattie. See, if the module tree is named 'B' then he can type "perl -MB ..." and get cool stuff to happen just by typing his initials. Frankly... I don't usually think of 'B' as short version of anything else. That's just it's name. Fun Fun Fun in the Fluffy Chair	[reply]
Re^4: Grabbing Variable Names by Aristotle (Chancellor) on Jan 12, 2003 at 14:55 UTC
"Optree". `:)` That's what I've mostly seen used by perlguts people. Makeshifts last the longest.	[reply]