Passing short value as parameter

[javanewbie83]

Hi every1,

i have a function that accepts short as an argument:

failedcount (short responcode){

switch(responcecode){
case 1:

case 2:

case 3:
}

}


now i have a method that calls it:

create {

failedcount(3) --- here it says can't pass an int value

}

so if i do:
short abc = 3;
and then do failedcount (abc);

Thank you..

[JT4NK3D]

are you saying if you do
short abc = 3;
failedcount(abc);
it still doesnt work?

[Eku]

Try converting abc into short datatype before sending it to failedcount();

[Eranga]

Quote:

Originally Posted by JT4NK3D

are you saying if you do
short abc = 3;
failedcount(abc);
it still doesnt work?

No he worried about that difference there. He can't directly pass a value, and he wants to so it. Don't like to use extra lines there.

[Eranga]

Call the method as follows.

Code:

failedcount((short)3);

[Eku]

thats the convertion i was talking about. =) Thats the simpliest answer. =) Im just wandering, why use short data type where you can use a int?

[Eranga]

That's his requirement.

[Eku]

^_^ I guess i can't argue with that. Please mark this thread [SOLVED] if we satisfied your question. =P

[Eranga]

Why can't you argue about that?

[ferranb]

A little offtopic, but take care about forgetting to use break statements on the case conditions.

Ferran

[Eranga]

That's depend on the implementations take place. In some cases need to have more than one case statements execute at a time.

[Nicholas Jordan]

Quote:

Originally Posted by Eranga

That's depend on the implementations take place. In some cases need to have more than one case statements execute at a time.

I wonder sometimes if the misplaced break in the 1-800 incident was someone placing a break where original code relied on simple jump-table into the switch. Sort of like (??) which can be either a tool or a tarantula.

[Eranga]

Actually using large number of case statements is bad practice, I think. I've never comes with such a situation more that 10 cases in a single application. But I've found someones code which have 30 cases, and that's the longest I've seen so far.

[Nicholas Jordan]

Quote:

Originally Posted by Eranga

Actually using large number of case statements is bad practice,

In general, yes. Especially when we get code like:

Code:

failedcount(3) // here it says can't pass an int value

but in my opinion building a lib that takes a list from a file ( or ram resident Collection ) and writes to a CharArrayOutputStream (${title}) would be of utility in acheiving the ability to build large switches.

Quote:

Originally Posted by Eranga

I think. I've never comes with such a situation more that 10 cases in a single application. But I've found someones code which have 30 cases, and that's the longest I've seen so far.

That's about the max that I could maintain by hand, an automated tool would be needful at that point.

[Eranga]

Quote:

Originally Posted by Nicholas Jordan

my opinion building a lib that takes a list from a file ( or ram resident Collection ) and writes to a CharArrayOutputStream (${title}) would be of utility in acheiving the ability to build large switches.

I agreed with you. I gave the same advice to one my friends to use large switches in one of his application. He says it's fine. Even I'm not use of it, seems to me that's the best way. Actually what I believe is working with streams in much easier, much safer.

Quote:

Originally Posted by Nicholas Jordan

That's about the max that I could maintain by hand, an automated tool would be needful at that point.

DO you know any such methodology I can use in such instances?

[Nicholas Jordan]

Quote:

Originally Posted by Eranga

DO you know any such methodology I can use in such instances?

It's early AM, still not awake yet, but I know from field experience that we are gonna recursively descend on Data Definitions, Type Definitions and Goal Definitions. What we will end up with is a TreeListControl, but we could have the rh view be a list of statements and the left-pane be the switch vals ( iow case n : ) the rh display would be what goes inside {}

We would need a prototype problem domain to do inital design concepting.

Creative Commons lic. Root word of license is lice. People who make license necessary won't bother to read the license. CC has accomplished a great and remarkable thawing of The Glacial Pace of Law. ( nomeclature from their field )

[Eranga]

Thanks, I'll check it and have a try. It may be really helpful to me in my projects too.