Question about variable scope static/non-static

Thread view:

Chris - 16 Apr 2005 16:17 GMT

I am working on my first program and I have a question about variable
scope and good programming practice.

I have an initial class where I have a 4 arrays of data. From there I
have a couple dialogs and frames that are used to enter or manipulate
or use the arrays.

I only ever expect to instantiate one of the main classes in this
program.

Is it better practice to create static arrays in the main class and
have the dialogs/frames access or manipulate the array?

I initially had it setup so I passed the arrays to each dialog and
retrieved the array data from public textfields from the dialog.

As far as speed, memory management or good programming practice, which
method is ideal? Thanks

Reply to this Message

HK - 16 Apr 2005 20:58 GMT

> I only ever expect to instantiate one of the main classes in this
> program.
>
> Is it better practice to create static arrays in the main class and
> have the dialogs/frames access or manipulate the array?

Even after three years of intensive Java programming I
sometimes run into this question: "hey, this class will
in a certain program only ever be instantiated once, so
why not make everything static."

I could not yet come up with a conclusive argument, except
that about half of the time I later realize that the
main class, after a bit of brushing up, could be
used as just a building block in another application.
Then typically some configuration parameters are added,
which go more naturally with a constructor than with
some init method to initialize the static stuff.

In the end I figured that it does not harm but may help
to build proper objects.

Harald.

Reply to this Message

Question about variable scope static/non-static

Free Magazines