nested class declarations?


Last Updated:

  1. mrqs

    mrqs Well-Known Member This Topic's Starter

    Joined:
    Sep 28, 2009
    Messages:
    1,446
    Likes Received:
    92
    i'm coming from a mainly c++/c# background and haven't done much with java, so this is something that caught my eye when looking at some simple examples of android code

    Code (Text):
    1. class GameView extends SurfaceView implements SurfaceHolder.Callback {
    2.     [COLOR="Red"]class GameThread extends Thread {
    3.         [...]
    4.     }[/COLOR]
    5.     private GameThread thread;
    6. [...]
    7. }
    this to my eyes is absolutely hideous and i'm wondering if you actually have to do it like this or if you can just make GameThread its own .java file and import that (moving the red part to a different file) ?

    if it has to be done like this, why?
    and if not, why would you?
     

    Advertisement
  2. alostpacket

    alostpacket Over Macho Grande? VIP Member

    Joined:
    Nov 29, 2009
    Messages:
    7,978
    Likes Received:
    3,603
    You can make it it's own class for sure, but I agree it's one of the most idiotic aspects of java.

    When I see anonymous callbacks or inner classes in a modern, strongly typed OOP language I wanna smack someone upside the head with a wet fish.

    Just wait until you see the SDK ;)
     
    mrqs likes this.

Share This Page

Loading...