Abhishek Bose

Swagato Bhatta wrote:

Minhaj kaimkhani wrote:well as i said before a class can have another class(i.e. Inner class) that can be declared as static;
example:
class Clazz{ static class subClazz{ //its a static inner class. static class subSubClazz{ //its another static inner class. } } }

in the above case Clazz is the most outer class.

Thank you

What if we declare a static class implementing a comparator<>?

import java.util.*; class SearchObjArray { public static void main(String [] args) { String [] sa = {"one", "two", "three", "four"}; Arrays.sort(sa); // #1 for(String s : sa) System.out.print(s + " "); System.out.println("\none = " + Arrays.binarySearch(sa,"one")); // #2 System.out.println("now reverse sort"); ReSortComparator rs = new ReSortComparator(); // #3 Arrays.sort(sa,rs); for(String s : sa) System.out.print(s + " "); System.out.println("\none = "+ Arrays.binarySearch(sa,"one")); // #4 System.out.println("one = "+ Arrays.binarySearch(sa,"one",rs)); // #5 } static class ReSortComparator implements Comparator<String> { // #6 public int compare(String a, String b) { return b.compareTo(a); // #7 } } }

Can we create an object of a static class?

[Edit - formatting]

Jeff Verdegan wrote:

Abhishek Bose wrote:
Thanks a lot... but i am still confused with return s.songName.compareTo(this.songName); how its working

What are you confused about. It's a method. It gets called. And, as the docs say, it returns negative, 0, or positive, to indicate that s.songName is less than, equal to, or greater than this.songName. (Which, by the way, is backwards for how one normally implements a comparison, but maybe somebody is doing a reverse sort.)

So what's your confusion?

According to my understanding in the first cycle this.songName gets value fastcar and s.songName gets the value falltopieces and then they get compared?

Viktor Kubinec wrote:First of all, you should follow java naming conventions ( class names should start with uppercase letter).

Second, your compareTo method implementation is not right (it is legal, but incorrect)

try this :

public int compareTo(songs s) { return this.songName.compareTo(s.songName); }

or this :

public int compareTo(songs s) { return s.songName.compareTo(this.songName); }


in compareTo method you should compare "this" object with s object. In your implementation you are comparing this object with itself, which makes no sense. To get a proper output you have to override toString method.

Thanks a lot... but i am still confused with return s.songName.compareTo(this.songName); how its working

import java.util.*; public class testing { public static void main(String[] args) { ArrayList<songs> lst = new ArrayList<songs>(); songs song1 = new songs("fastcar", "tracychampman"); songs song2 = new songs("fall to pieces","Avril"); songs song3 = new songs("The animal song","Savage Gardens"); lst.add(song1); lst.add(song2); lst.add(song3); System.out.print(lst); Collections.sort(lst); System.out.print(lst); } } class songs implements Comparable<songs> { String songName; String Movie; songs(String songName,String Movie) { this.songName=songName; this.Movie=Movie; } public int compareTo(songs s) { return songName.compareTo(songName); } }


I wrote this code but what is getting displayed is
[songs@addbf1, songs@42e816, songs@9304b1][songs@addbf1, songs@42e816, songs@9304b1]

Can somebody explain me why this is happening? Also in the comaprerTo method [return songName.compareTo(songName); falltopieces is comparing with falltopieces] its like comparing a song name with itself, Then what the use of compareTo()?

Hello EveryOne,

I am not clear with this HAs- A relationship in java....can anyone please explain me..... i request a detailed version of the explaination.....!

how are opcodes related to java..?

If a inner class is declared in the method of the outer class and it has a local variable then why it must be declared as Final...?

I have Read that java is secure because of its JVM that protects it..... what actually jvm does to make java secure....???

Buddhika Mawella wrote:When a java program is compiling there is nothing called heap or stack. Stack and heap only exist on runtime.

So that means each and every member in a java program gets on to the heap during runtime and not before..?

Buddhika Mawella wrote:There is nothing called 'loading' when compiling. Compiling a java program is just converting your human readable java code in to a machine readable language when interpreted by JVM.

i mean when it gets on to heap.....!

Static members are loaded at runtime or compile time.....??

what is embedded java.?

Can any how strings can be made mutuable.....?