Skip to content

free Ptr{Cstring} when we need to. #77

Description

@visr

Came up in #75 (comment).
We currently never free the memory, resulting in a (probably small) memory leak.

In aftercare(::Ptr{Cstring}) we should free this at least in the case of CPLGetConfigOptions, but we should probably review all functions that return Ptr{Cstring}

See also 259a27c

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions