int[]

[dick_nl]

Using a decompiler I figured out that they don't display the values of an array like "int[] myInts = {1,2,3,4};"

Are they just difficult to reverse engineer (and for that reason a good base for protection)?

[Robby]

I don't understand your question.

[dick_nl]

What I mean is the following:

 

The next code (C#):

public void func()
{
int[] arrayOfInt = {1,2,3,4, 10};
int sample = arrayOfInt[3] * arrayOfInt[4] ;
// sample should be 40 now
}

 

is in the decompiler visible as:

public void func()
{
int[] arrayOfInt;
int sample = arrayOfInt[3] * arrayOfInt[4] ;
}

 

So the values that are, in the code, stored in the array aren't made readable in the decompiler... Is that always the case!?

Edited March 2, 2004 by dick_nl

[divil]

It just means the decompiler you used doesn't know how to reconstruct the array initialization.

[dick_nl]

But so far I didn't find a decompiler that could... does anybody know a decompiler that could?

[divil]

I'm no expert on what the different decompilers can or cannot do, but the initialization will certainly be visible in a disassembly so don't get the idea that your code is protected in some way.

[dick_nl]

It would already had suprised me! Although in the disassembler from M$ I couldn't see it too... but probably there's a way to figure it out...