I'm working on a source code analyzer in perl. Its job is to analyze source code for security. I thought that the best way to parse the source would be to use one of the B modules. However, they seem to get into the very nitty gritty perlguts, which is beyond me. My prog does not need to know every detail of the source - basically, just when any variable is assigned, used to assign a value to another variable, or passed to a sub. (This is, btw, much more than B::Xref tells you). It should also be able to recognize (somewhat) when these things are done indirectly, like with $_ (which is all important, as this is how subs work), references, lists, foreach loops, etc. Can anyone suggest a simpler way to do this? Like I said the B:: 's that deal with the tree go into *alot* of implementation detail, which is beyond me. If not, can someone suggest a text which explains what's going on? Most of the perlguts texts that I've seen focus on the SV, HV, 's etc - I need to know about how assignements are made and values are handled. The textual tree included in the perldoc perlguts is about on target - is there anyway of accessing its equivalent progamatically? Thanks in advance, Franklin DeMatto [EMAIL PROTECTED] qDefense - DEFENDING THE ELECTRONIC FRONTIER
