ansaurus

Question

Answer 1

+2 A:

You haven't told us what refno is. Is that really all one switch case? You can set breakpoints in your code and debug it (F11 in Eclipse) to be able to step through your code and see exactly which execution path it takes.

David Hedlund 2010-09-16 11:10:24

refno is an integer

bindal 2010-09-16 11:14:10

i got that from context, yeah. you really need to be more specific, but regardless, following my example should get you all the information you need as to why your code isn't being executed

David Hedlund 2010-09-16 11:15:27

Answer 2

A:

For what value of refno is it not executed? (I see there is no default case in your switch)
Don't Repeat Yourself... all that repetitive code! You will gain a lot of time if you create a "find_and_print" function, an a dispatch table that calls that function with the proper arguments.

Here is some pseudo-code.

void find_in_array_and_print( String[] strings, String value ) {
   for (int i = 0; i < strings.length; i++) {
     if (strings[i]==value ) {
        prs = i;
        System.out.println("prs"+prs);
        System.out.println("i"+i);
     }
   }    
}

String[] to_look_in( int refno ) {
   switch( refno ) {
     case 0: return R.array.strtemp409A;
     case 1: return R.array.strtemp414B;
     //...
   }
}

find_and_print( GetResources().getStringArray( to_look_in( refno ) ), str );

xtofl 2010-09-16 11:19:41

for all the values

bindal 2010-09-16 11:21:34

Answer 3

A:

For that piece of code, the only way you don't get in the switch is if an exception is thrown between the first line and the switch. If you are sure that you even enter that piece of code.

A possible cause of exceptions? Out of memory, null pointer dereference are the first ones that come to mind regarding the limited set of statements.

xtofl 2010-09-16 11:34:37

*"In my program this is one switch case"* <- unless *all of it* really is one switch case, which is not being hit.

David Hedlund 2010-09-16 12:44:50

Answer 4

A:

I don't know how you are setting refno, but the auto generated R.java won't start at 0. If you want to trap it add a default: case to your switch. Finally "==" is NOT the way to compare Strings in Java. It won't always work. Try running this as an example and see what happens!

    String s1 = new String("123");

    String s2 = new String("123");
    if (s1 == s2) 
        System.out.println("s1 == s2 SHOWS TRUE");
    else
        System.out.println("s1 == s2 SHOWS FALSE");
    if (s1.equals(s2)) 
        System.out.println("s1.equals(s2) SHOWS TRUE");
    else
        System.out.println("s1.equals(s2) SHOWS FALSE");

Then Google for WHY it doesn't work and why you should use .equals()

NickT 2010-09-16 12:46:50

ansaurus

tags:

views:

answers:

android datatype casting

related questions