1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374 |
- /* idn-free.h --- Invoke the free function to release memory
- Copyright (C) 2004-2024 Simon Josefsson
- This file is part of GNU Libidn.
- GNU Libidn is free software: you can redistribute it and/or
- modify it under the terms of either:
- * the GNU Lesser General Public License as published by the Free
- Software Foundation; either version 3 of the License, or (at
- your option) any later version.
- or
- * the GNU General Public License as published by the Free
- Software Foundation; either version 2 of the License, or (at
- your option) any later version.
- or both in parallel, as here.
- GNU Libidn is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
- General Public License for more details.
- You should have received copies of the GNU General Public License and
- the GNU Lesser General Public License along with this program. If
- not, see <https://www.gnu.org/licenses/>. */
- #ifndef IDN_FREE_H
- # define IDN_FREE_H
- /**
- * SECTION:idn-free
- * @title: idn-free.h
- * @short_description: Memory deallocation functions
- *
- * Memory deallocation functions.
- */
- # ifndef IDNAPI
- # define IDNAPI
- # endif
- # ifdef __cplusplus
- extern "C"
- {
- # endif
- /* I don't recommend using this interface in general. Use `free'.
- *
- * I'm told Microsoft Windows may use one set of `malloc' and `free'
- * in a library, and another incompatible set in a statically compiled
- * application that link to the library, thus creating problems if the
- * application would invoke `free' on a pointer pointing to memory
- * allocated by the library. This motivated adding this function.
- *
- * The theory of isolating all memory allocations and de-allocations
- * within a code package (library) sounds good, to simplify hunting
- * down memory allocation related problems, but I'm not sure if it is
- * worth enough to motivate recommending this interface over calling
- * `free' directly, though.
- *
- * See the manual section 'Memory handling under Windows' for more
- * information.
- */
- extern void IDNAPI idn_free (void *ptr);
- # ifdef __cplusplus
- }
- # endif
- #endif /* IDN_FREE_H */
|