Re: Bug in documentation: Gio::File Class Reference

[Alwin Leerling <dna leerling gmail com>]

On Wed, 2016-08-03 at 23:41 +0100, Jonathan Wakely wrote:
> On 3 August 2016 at 23:38, Alwin Leerling wrote:
> > I believe I may have found some errors in the reference
> > documentation
> > of the Gio::File Class:
> >
> > Function signatures
> >
> > std::string Gio::File::get_basename() const
> > std::string Gio::File::get_path() const
> > std::string Gio::File::get_relative_path(
> >                 const Glib::RefPtr< const File & descendant >
> >                                 ) const
> > std::string Gio::File::get_uri() const
> >
> > are all declared returning a const std::string.
>
> No they aren't, those return non-const std::string objects.

Of course, my bad. Forgive my momentary lapse of reasoning. Still,
should you free std::string objects?

Alwin

(Not a heavy mailing list user. Replied to Jonathans message and forgot
to add the mailing list address. Posted it here fore completeness)