BUG: 10.1.3 EA1 - Refactor errors when handling arrays

Question

Hi,
I declare my arrays like this:
int n[];
Rather than the way JDeveloper likes it:
int[] n;
So when JDeveloper refactors my code I either get too many [] or not enough.
E.g, JDeveloper makes a method out of some code, or moves definitions up the class hierarchy and it ends up like this:
int[] n[];
Its like it knows it's an array so it writes "int[]" then it writes the variable as it originally found it "n[]". I have also seen it drop the [] in a method parameter argument that was an array.
JDeveloper should preserve my definitions the way they were or at least get them right if it insists on changing it to its own style.
Regards,
Simon.

Answer 1

Thanks for looking into it.
You have to split the array definition from the method code so that it has to pass the array as a parameter.
E.g.
String s;
Object i[] = new Object[3];
if(i==null || i.length == 0)
s = "i is null";
System.out.println(s + i.toString());
Leave the definitions behind and just make a method of just the if statement. Mine generated:
String s;
Object i[] = new Object[3];
s = test(i);
System.out.println(s + i.toString());
and
private String test(Object i)
String s;
// TODO type initialisation here
if(i==null || i.length == 0)
s = "i is null";
return s;
Note that 'int i' is wrong and causes the syntax errors.
If you change the definition to "int[] i;" it works OK.
It also works if you include the definition (as it was) in the refactor code.
The indenting of the new method was mucked up too. Not as shown here because this forum strips out all leading blanks. Indenting appears to get mucked up if you have set the tabstop and indent set to 4 in the preferences. A 'reformat' fixes it.
Cheers,
Simon.