Array declaration compiler bug?

Thread view:

Kenneth P. Turvey - 09 Apr 2006 03:57 GMT

I noticed today that a program I've written has different behavior when
one of the variables is declared as:

int outPixel[]

instead of

int[] outPixel

Shouldn't these exhibit exactly the same behavior all the time?

- --
Kenneth P. Turvey <kt-usenet@squeakydolphin.com>

XMPP IM: kpturvey@jabber.org
Yahoo IM: kpturvey2

Reply to this Message

Patricia Shanahan - 09 Apr 2006 04:48 GMT

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
[quoted text clipped - 9 lines]
>
> Shouldn't these exhibit exactly the same behavior all the time?

It is very difficult to say from a code snippet. For example:

int outPixel[],y;

and

int[] outPixel,y;

are different. Can you produce a complete, self-contained example?

Patricia

Reply to this Message

Kenneth P. Turvey - 09 Apr 2006 06:20 GMT

> It is very difficult to say from a code snippet. For example:
>
[quoted text clipped - 5 lines]
>
> are different. Can you produce a complete, self-contained example?

Yes, I understand the difference of that above. I'll see if I can get
something small to work over the next week and post something at that
time. The complete statement was:

int[] outPixel = new int[]{0, 0, 0};

and

int outPixel[] = new int[]{0, 0, 0};

This was followed by a looping construct that works fine for the first
line, but seems to use a newly initialized array for each iteration when
the second declaration is used.

The scoping is all wrong.

- --
Kenneth P. Turvey <kt-usenet@squeakydolphin.com>

XMPP IM: kpturvey@jabber.org
Yahoo IM: kpturvey2

Reply to this Message

Mike Schilling - 09 Apr 2006 18:51 GMT

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
[quoted text clipped - 24 lines]
>
> The scoping is all wrong.

If that's really the only difference, you might try disassembling the
resulting code with javap -c and seeing if that gives you any clues.

Reply to this Message

Array declaration compiler bug?

Free Magazines