Ben Aurel a écrit :
hi
I have simple neko script:
$ cat hello.neko
s = "hello";
$print(s);
If I compile this it with:
$ nekoc hello.neko
I get a neko bytecode file:
$ cat hello.n
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@5i1L/-X<8b>È
Hmm ... pretty obfuscated, but I think that there have to be some
opcode instructions - no? Something like
...
0x0000408C [1] add 2 0 1
0x0100009E [2] return 2 2
0x0080001E [3] return 0 1
...
Is it possible to make that visible? If I'm right with the existance
of opcodes, how to produce this obfuscated code, and why?
nekoc -d hello.n
This will create a .dump that contains the bytecode.
Bytecode is needed by the VM to execute the code and then can't be
obfuscated. However using "nekoc -z hello.n" will remove debug
informations and global names, if that's useful for you.
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
