Skip to main content

desending sort algo

...
double []test = new double []{88.6,88.9,-1,25,88.6};
int size = test.length;

System.out.println("*** un-sorted ***");
for (double d : test){
System.out.println(d);
}

// descending sort algo *************************************
int counter = 0;
int indexOfMax = 0;

// after each iteration of while, test[counter] should have the correct value
while (counter < size){
indexOfMax = counter; // assuming that test[counter] has the max value
// this loop finds the index of max value (stores in indexOfMax) from the test array starting from index counter+1
for(int i = counter+1; i < size; i++){
if (test[i]>test[indexOfMax]){
indexOfMax = i;
}
} // end of for loop -- now indexOfMax should have the max value

// swapping
double tmp = test[counter];
test[counter] = test[indexOfMax];
test[indexOfMax] = tmp;
counter++;
}
// end of algo *********************************************

System.out.println("*** sorted ***");
for (double d : test){
System.out.println(d);
}
...

Comments

Popular posts from this blog

svn credentials caching

SVN client has a built-in system for caching authentication credentials on disk. It saves the credentials in the user's private runtime configuration area ~/.subversion/auth/ (Unix-like systems) %APPDATA%/Subversion/auth/ (Windows) If you dont want to catch the credeitials for a commit, use --no-auth-cache. $ svn commit --no-auth-cache Here we are telling the svn client that dont cach authentication credentials. You can disable credential caching permanently by editing your runtime config file (located next to the auth/ directory). Set store-auth-creds to no. [auth] store-auth-creds = no

log4j - use logger instead of category

Do not use 'category'. In log4j 1.2, the Category class has marked as being deprecated and has been replaced by the Logger class. I am using log4j-1.2.14.jar and category didn't work for me. Example: <logger name="com.test.pkg1"><level value="INFO"/></logger> <logger name="com.test.pkg2"><level value="INFO"/></logger> Was: <category name="com.test.pkg1"><priority value="INFO"/></category> <category name="com.test.pkg2"><priority value="INFO"/></category>

Java Data Objects

JDO has nothing to do with where methods are executed. JDO simply specifies how the fields of a petent object should be managed in-memory, being transparently stored to and retrieved from an underlying datastore. With JDO, methods are invoked on persistent object by an application, as per any regular in-memory Java object. JDO has many implementations. Visit the following link to know about the available implementations. http://db.apache.org/jdo/impls.html