Skip to main content

Creation of Arrays in Java (The C++ Style)


Why can't we make arrays in Java like this:




int marks[5];



And assign values after this declaration?



Anyone please explain the terminology or difference.


Source: Tips4allCCNA FINAL EXAM

Comments

  1. This is because there are no stack arrays in Java. Here is Java equivalent:

    int[] marks = new int[5];


    It looks a lot like allocating dynamically-sized arrays in C++. Of course you don't have to worry about calling a delete[], because it's garbage collected.

    ReplyDelete
  2. Because the syntax you're citing allocates the array on the stack, and Java arrays are objects, and all Java objects are allocated on the heap (modulo recent JVM optimizations, but those are implicit).

    And it pretty much has to be that way in a language without manual memory management because stack-allocated stuff disappears when the call returns, leading to dangling pointers, and a fundamental feature of Java is not to allow stuff like that.

    Of course one could argue that Java should use the stack allocation syntax to do heap allocation, but that would have confused the heck out of anyone who knew C - not good.

    ReplyDelete
  3. In Java the size of the array is determined by the expression that creates it, e.g.:

    int[] marks = new int[5];


    or

    int[] marks = {1,2,3,4,5};




    Note also that although the syntax int marks[] is allowed in Java (Java has several such rules for compatibility with C++), it is not recommended, the syntax int[] marks is more idiomatic and thus preferred.

    ReplyDelete
  4. int marks[] = new int[]{1, 2, 3};

    ReplyDelete
  5. Because arrays are Object-s (inheriting from the Object class). And to create an object you have to use the new keyword. (Most of the time).
    I think the reason behind the new keyword is to denote that the variables are references to dynamically allocated instances.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex