🚀 go-pugleaf

In article <3vq5so$8td@wsrcom.wsr.ac.at> hjp@wsrdb.wsr.ac.at (Peter Holzer) writes:
> You cannot return multiple values in C anyway, so this is moot. You

Sure it is moot, but this discussion is about possible extensions to C, not
about the current standard (the thread started out as an advocacy of named
return parameters, and I noted that those were only worthwhile if multiple
results were allowed). I think that named return parameters would simplify
(or at least orthogonalize) the language, but that's very much a matter of
taste.

> can return a structure and are free to initialize only some of its
> fields. And you are also free to change or not change locations to
> which pointers are passed to the function.

Yup, but both solutions introduce inefficiencies, as they practically (*)
forbid the compiler to use registers for passing back the results. Plus,
both options look clumsy (another big IMHO, of course).

-- Markus