On Sun, May 17, 2015 at 2:30 PM, Andre Somers <an...@familiesomers.nl> wrote: > In the spirit of option b), would it be an option to have the method > take a QString& instead of a QString*? That would resolve the ambiguity.
It would solve, but Qt APIs use pointers instead of references for out-arguments (and that's a very good code policy). Cheers, -- Giuseppe D'Angelo _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development