Linked by Bjorn Raupach on Thu 17th Jul 2008 06:01 UTC
Today was one of those days when I wished Java would support multiple return values. I had to develop a rather CPU-intensive algorithm which would compute a solution for a knotty constraint problem. Having a solution alone is sometimes not enough and you also need to add some parameters which measure the quality of the computed outcome. Most of these accompanying parameters can or have to be computed within the algorithm itself, but Java allows you to return only one value either an object or a primitive type. People working with Lisp, MATLAB or Perl, just to mention a few, don't have a problem like this at all. Functions supporting multiple return values is already implemented at the language level and frameworks make heavy use of this. But as a Java programmer you are pretty much stuck here and need to consider some other means to come out of this situation. In the following I would like to give some hints on that topic. Hopefully they are of help for anyone having the same problem every now and then.
Thread beginning with comment 323625
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:
2005-07-06
Bleah, I don't like C++'s overloading of keywords for type and method signature..
Not always: if there's another reference with read-write access to the same object, it can be modified or the const may be casted away.
Yup, but it caused many, many discussions: head vs tail const, const vs invariant.. Const is a concept really hard to design properly.
And the solution retained is ineleguant as for C++ compatibility's sake, the name const is retained for read-only views (which may not be really constant!), and true constants are named 'invariant'.
IMHO 'const' should be replaced by 'view' as in "view but don't touch (others may do it though)"
and true constant named const.