aspose file tools*
The moose likes Beginning Java and the fly likes Very basic instance addressing question Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Java » Beginning Java
Bookmark "Very basic instance addressing question" Watch "Very basic instance addressing question" New topic
Author

Very basic instance addressing question

Bill Parsh
Greenhorn

Joined: Nov 20, 2008
Posts: 9
Say I have a "MainWindow" instance that creates a "Scorekeeper" instance and many "Player" instances. If I want the Player instances to be able to address the Scorekeeper instance, the way I do it now is instantiate the Scorekeeper in the MainWindow, then when I create a Player I pass the EDIT: MainWindow /EDIT as a parameter to the Player constructor. Then I address the Scorekeeper from the Player as like "myMainWindow.myScorekeeper"

This works fine but seems a little wonky to me. Any suggestions?
[ November 20, 2008: Message edited by: Bill Parsh ]
Ernest Friedman-Hill
author and iconoclast
Marshal

Joined: Jul 08, 2003
Posts: 24168
    
  30

Hi Bill,

Welcome to JavaRanch!

Sounds like you're passing the window to the player, not the scorekeeper; otherwise in player you'd just use "myscorekeeper" or something, right?

But in any case, that's basically the right way to do things: either provide player with what it needs as constructor arguments, and let the player store a reference for its lifetime, or alternatively, make sure all the player methods that need a scorekeeper accept one as an argument, so that the caller has to provide the scorekeeper.

A third alternative -- and one that's strongly discouraged -- is to store things in public static variables, so that the player objects can just say, for example, MainWindow.theScoreKeeper to access that static variable. The problem with this is that your code becomes terribly messy, complex, interconnected and impossible to change after a while.


[Jess in Action][AskingGoodQuestions]
Bill Parsh
Greenhorn

Joined: Nov 20, 2008
Posts: 9
Originally posted by Ernest Friedman-Hill:
Sounds like you're passing the window to the player, not the scorekeeper; otherwise in player you'd just use "myscorekeeper" or something, right?


Right, sorry about that.
Campbell Ritchie
Sheriff

Joined: Oct 13, 2005
Posts: 36592
    
  16
Originally posted by Ernest Friedman-Hill:
. . . basically the right way to do things


No need to be sorry; EFH said you are basically right, just needing a bit of refinement
J. Noah
Greenhorn

Joined: Nov 15, 2008
Posts: 9
Depending on the app, another thing you could do is create a singleton for the scorekeeper or mainwindow if that's applicable in this case. That way you'd be able to access it elsewhere while still preserving some of the ideal loose coupling properties.


<a href="http://blog.expensivedna.com" target="_blank" rel="nofollow">http://blog.expensivedna.com</a>
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Very basic instance addressing question
 
Similar Threads
Step to deploy and run EJB3.0 in jboss Clustered instance
How should I return an array of a class type?
Interface - not implemented
Java Monopoly game design..
Head First Java Guessing Game