How to use switch statement that involves instantiation in cases?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I have an instance variable piece that is of type Object. It is instantiated as one of several classes in my program as a part of a switch statement as follows:



public Object getRandomPiece() {
int random = (int)(Math.random()*8);
switch(random) {
case 0: case 1:
_piece = new Piece1();
}
return _piece;
}


Note that there are multiple cases, I have just summarized it in this snippet. My problem is that after giving _piece its value from the switch statement and returning it, I cannot access any of its new class's methods (example, methods from class Piece1). How should I approach this?










share|improve this question




















  • 3





    Program to a common Piece interface. Also, you could just return new Piece1();

    – Elliott Frisch
    Nov 17 '18 at 3:15


















0















I have an instance variable piece that is of type Object. It is instantiated as one of several classes in my program as a part of a switch statement as follows:



public Object getRandomPiece() {
int random = (int)(Math.random()*8);
switch(random) {
case 0: case 1:
_piece = new Piece1();
}
return _piece;
}


Note that there are multiple cases, I have just summarized it in this snippet. My problem is that after giving _piece its value from the switch statement and returning it, I cannot access any of its new class's methods (example, methods from class Piece1). How should I approach this?










share|improve this question




















  • 3





    Program to a common Piece interface. Also, you could just return new Piece1();

    – Elliott Frisch
    Nov 17 '18 at 3:15














0












0








0








I have an instance variable piece that is of type Object. It is instantiated as one of several classes in my program as a part of a switch statement as follows:



public Object getRandomPiece() {
int random = (int)(Math.random()*8);
switch(random) {
case 0: case 1:
_piece = new Piece1();
}
return _piece;
}


Note that there are multiple cases, I have just summarized it in this snippet. My problem is that after giving _piece its value from the switch statement and returning it, I cannot access any of its new class's methods (example, methods from class Piece1). How should I approach this?










share|improve this question
















I have an instance variable piece that is of type Object. It is instantiated as one of several classes in my program as a part of a switch statement as follows:



public Object getRandomPiece() {
int random = (int)(Math.random()*8);
switch(random) {
case 0: case 1:
_piece = new Piece1();
}
return _piece;
}


Note that there are multiple cases, I have just summarized it in this snippet. My problem is that after giving _piece its value from the switch statement and returning it, I cannot access any of its new class's methods (example, methods from class Piece1). How should I approach this?







java switch-statement






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 17 '18 at 3:18









John Kugelman

249k54407460




249k54407460










asked Nov 17 '18 at 3:13









JabrahJabrah

21




21








  • 3





    Program to a common Piece interface. Also, you could just return new Piece1();

    – Elliott Frisch
    Nov 17 '18 at 3:15














  • 3





    Program to a common Piece interface. Also, you could just return new Piece1();

    – Elliott Frisch
    Nov 17 '18 at 3:15








3




3





Program to a common Piece interface. Also, you could just return new Piece1();

– Elliott Frisch
Nov 17 '18 at 3:15





Program to a common Piece interface. Also, you could just return new Piece1();

– Elliott Frisch
Nov 17 '18 at 3:15












1 Answer
1






active

oldest

votes


















1














Program to a common Piece interface. If you don't use object state, prefer to make your method static. I would prefer a ThreadLocalRandom over Math.random(), and I would prefer to avoid unnecessary local temporary variables. Putting that together, it might look something like



public static Piece getRandomPiece() {
switch (ThreadLocalRandom.current().nextInt(8)) {
case 0: case 1:
return new Piece1();
}
return null;
}





share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53347856%2fhow-to-use-switch-statement-that-involves-instantiation-in-cases%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    Program to a common Piece interface. If you don't use object state, prefer to make your method static. I would prefer a ThreadLocalRandom over Math.random(), and I would prefer to avoid unnecessary local temporary variables. Putting that together, it might look something like



    public static Piece getRandomPiece() {
    switch (ThreadLocalRandom.current().nextInt(8)) {
    case 0: case 1:
    return new Piece1();
    }
    return null;
    }





    share|improve this answer




























      1














      Program to a common Piece interface. If you don't use object state, prefer to make your method static. I would prefer a ThreadLocalRandom over Math.random(), and I would prefer to avoid unnecessary local temporary variables. Putting that together, it might look something like



      public static Piece getRandomPiece() {
      switch (ThreadLocalRandom.current().nextInt(8)) {
      case 0: case 1:
      return new Piece1();
      }
      return null;
      }





      share|improve this answer


























        1












        1








        1







        Program to a common Piece interface. If you don't use object state, prefer to make your method static. I would prefer a ThreadLocalRandom over Math.random(), and I would prefer to avoid unnecessary local temporary variables. Putting that together, it might look something like



        public static Piece getRandomPiece() {
        switch (ThreadLocalRandom.current().nextInt(8)) {
        case 0: case 1:
        return new Piece1();
        }
        return null;
        }





        share|improve this answer













        Program to a common Piece interface. If you don't use object state, prefer to make your method static. I would prefer a ThreadLocalRandom over Math.random(), and I would prefer to avoid unnecessary local temporary variables. Putting that together, it might look something like



        public static Piece getRandomPiece() {
        switch (ThreadLocalRandom.current().nextInt(8)) {
        case 0: case 1:
        return new Piece1();
        }
        return null;
        }






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 17 '18 at 3:29









        Elliott FrischElliott Frisch

        157k1397192




        157k1397192
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53347856%2fhow-to-use-switch-statement-that-involves-instantiation-in-cases%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Xamarin.iOS Cant Deploy on Iphone

            Glorious Revolution

            Dulmage-Mendelsohn matrix decomposition in Python