Maxim Kasimov wrote:
by the way, goto statement will be useful for writing more powerful
obfuscators
Let me get that clear: you want a goto to help with debugging.
And you want to obfuscate your code even more?
!?
Perhaps you need to write in Perl, or some other similar language.
Writing in
André Roberge wrote:
Maxim Kasimov wrote:
by the way, goto statement will be useful for writing more powerful
obfuscators
Let me get that clear: you want a goto to help with debugging.
And you want to obfuscate your code even more?
!?
Perhaps you need to write in Perl, or some other similar
Maxim Kasimov wrote:
André Roberge wrote:
Maxim Kasimov wrote:
by the way, goto statement will be useful for writing more powerful
obfuscators
Let me get that clear: you want a goto to help with debugging.
And you want to obfuscate your code even more?
!?
Perhaps you need to write in Perl, or
On 4/20/05, Robert Kern [EMAIL PROTECTED] wrote:
Maxim Kasimov wrote:
André Roberge wrote:
Maxim Kasimov wrote:
by the way, goto statement will be useful for writing more powerful
obfuscators
Let me get that clear: you want a goto to help with debugging.
And you want to
Bill Mill wrote:
I believe he meant obfuscating bytecode for a commercial product, to
try and avoid decompilation, which is often a desirable function for
commercial entities.
there is no shortage of jump instructions on the bytecode level, so if he
wants
to obfuscate bytecode, all he has to do
Maxim Kasimov wrote:
André Roberge wrote:
Maxim Kasimov wrote:
by the way, goto statement will be useful for writing more powerful
obfuscators
Let me get that clear: you want a goto to help with debugging.
And you want to obfuscate your code even more?
!?
Perhaps you need to write in Perl, or
