in reply to Obfuscating method calls

I guess he meant one could change the method name (and every invocation of said method) to something hard to read and without reference to what the method actually does. For instance, change

sub average { ... } ... print average( ... )
to
sub xyyxwx { ... } ... print xyyxwx( ... )

Of course this would be only one of several tricks (and not a particularly successful one) in a code obfuscator.

Cheers

Antonio

The stupider the astronaut, the easier it is to win the trip to Vega - A. Tucket

Replies are listed 'Best First'.
Re: Re: Obfuscating method calls
by diotalevi (Canon) on Jun 24, 2003 at 14:41 UTC

    I must not have been clear. The reason ->request was not originally altered was because it belongs to the LWP package which is obviously not up for changing by the host module.