Wouldn't the Builder pattern address this issue? So you can do:
object.setName("Alfred E. Neumann") .setLink("http://blog.schauderhaft.de) .setUltimateAnswer(42) .setTempFile("c:\\temp\\x.txt") .setZip(23);
object.setName("Alfred E. Neumann") .setLink("http://blog.schauderhaft.de) .setUltimateAnswer(42) .setTempFile("c:\\temp\\x.txt") .setZip(23);
Javascript APIs hack this in by taking Objects as params so that you can do {name='Alfred E. Neuman'...}. Unfortunately, Java's syntax isn't nice for creating Maps either, but maybe you could do something with that.
In the end, this seems like a problem with the language syntax and any fix other than one at the language level is going to be a hack.
o.doSomething({
name : "Alfred E. Neumann",
link : "http://blog.schauderhaft.de,
ultimateAnswer: 42,
tempFile: "c:\\temp\\x.txt",
zip : 23});It's not addressing named parameters issue, but I find it better like this.