Use the Integer type to pass the value:

Integer ai,bi;call_function (ai, bi);int a = ai, b = bi;

Skizz

Similarly if you want to pass objects by reference you would have to wrap them.

class Output
{
Object value;
}

...

public void doSomething(Output o1, Output o2)
{
...
}

It's not nice, but it works.. Using java 1.5 you could make it better though by specifying the type of value.

I use Thex0's method, and if it's a primitive I further wrap it in it's appropiate class, or make a special IntOutput that has an int instead of an object. And yes, it does looks bad.

shmoove

Quote:Original post by MindWipe
Alright, I've been coding with java for a while. I'm a professional j2me developer. But being a C/C++ at heart I have some problems.

And there is the heart of your problem - you are not programming in java at all here, but in C. Go read Bruce Eckel's "thinking in java" (it's free if you read it online). If you find you know whole sections, skip them; you will probably find quite a lot of useful stuff you hadn't quite stopped to think about before (esepcially if you normally use J2ME instead of J2SE).

Quote:
Ok, I understand java does not support pointers and allways sends objects/arrays/?????? as references, but not variables.

Everything in java is pass-by-reference EXCEPT for "basic datatypes" (int, short, long, boolean, char, byte, float, double - which are unique because they are the ONLY types in java that are java keywords, so they're easy to distinguish), which are pass-by-value.

The real question, though, is what the heck are you TRYING to do? Rather than us telling you how to do a C thing in java, tell us what you are trying to do in terms of programming and we can tell you the best/easiest/fastest way to do that *in java*...

This:

Quote:


class MyClass
{
int X;
}

public void SetA( MyClass mc )
{
mc.x = 10;
}

...is a bastardization of a standard OOP pattern: you appear not to fully understand OOP with that method! The *whole point* of OOP is that you do NOT EVER write methods that take a class and set it's values: those methods MUST be inside the class itself (OK, the compiler doesn't care, and there are instances where you violate this legitimately, but the point of OOP is not to do this...).

So, you ought instead to have a method in MyClass which is:

public void setX( int newx )
{
x = newx;
}

Maybe understanding OOP is all you need, but maybe you're trying to do something more cunning (I'm assuming the former since it's more likely, statistically! Apologies if I've inadvertently patronized you!). If it's the latter, tell us what you are doing in a bigger sense and then we'll be able to help better...

redmilamber (who managed to stay logged in for almost 2 days this time - seems GD.net cookies have been improved - but then GD.net staff broke it again and it is now IMPOSSIBLE for me to login )