Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

Re^2: Deparse isn't as reliable as I thought

by diotalevi (Canon)
on Mar 04, 2006 at 06:03 UTC ( #534427=note: print w/ replies, xml ) Need Help??


in reply to Re: Deparse isn't as reliable as I thought
in thread Deparse isn't as reliable as I thought

Deparse doesn't parse perl either. It generates perl. Every time Deparse fails to produce source code that compiles back to the same thing, that's a bug. There are no obfuscations that should be undeparseable.

⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊


Comment on Re^2: Deparse isn't as reliable as I thought
Replies are listed 'Best First'.
Re^3: Deparse isn't as reliable as I thought
by truedfx (Monk) on Mar 04, 2006 at 09:17 UTC
    What about BEGIN { close STDOUT; }? (No, I'm not entirely serious here.)

      You might as well be. To deparse that, you'd want B::Deparse to be able to write to a file instead of just STDOUT.

      ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

        Yeah, I suppose you're right that that can be worked around. How about a more extreme example then?

        BEGIN { undef %:: if %O:: }

        I don't think there's any way to deparse that.

Re^3: Deparse isn't as reliable as I thought
by Steve_p (Priest) on Mar 04, 2006 at 13:41 UTC

    Agreed. Several modules depend on the proper functioning of B::Deparse. If there is a difference, you should report the bug with perlbug. Please provide the test scripts so this can problem can be investigated.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://534427]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (15)
As of 2015-07-31 17:49 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (279 votes), past polls