libidn 1.43

idn-free.h
Go to the documentation of this file.
1/* idn-free.h --- Invoke the free function to release memory
2 Copyright (C) 2004-2025 Simon Josefsson
3
4 This file is part of GNU Libidn.
5
6 GNU Libidn is free software: you can redistribute it and/or
7 modify it under the terms of either:
8
9 * the GNU Lesser General Public License as published by the Free
10 Software Foundation; either version 3 of the License, or (at
11 your option) any later version.
12
13 or
14
15 * the GNU General Public License as published by the Free
16 Software Foundation; either version 2 of the License, or (at
17 your option) any later version.
18
19 or both in parallel, as here.
20
21 GNU Libidn is distributed in the hope that it will be useful,
22 but WITHOUT ANY WARRANTY; without even the implied warranty of
23 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
24 General Public License for more details.
25
26 You should have received copies of the GNU General Public License and
27 the GNU Lesser General Public License along with this program. If
28 not, see <https://www.gnu.org/licenses/>. */
29
30#ifndef IDN_FREE_H
31# define IDN_FREE_H
32
41# ifndef IDNAPI
42# if defined LIBIDN_BUILDING && defined HAVE_VISIBILITY && HAVE_VISIBILITY
43# define IDNAPI __attribute__((__visibility__("default")))
44# elif defined LIBIDN_BUILDING && defined _MSC_VER && ! defined LIBIDN_STATIC
45# define IDNAPI __declspec(dllexport)
46# elif defined _MSC_VER && ! defined LIBIDN_STATIC
47# define IDNAPI __declspec(dllimport)
48# else
49# define IDNAPI
50# endif
51# endif
52
53# ifdef __cplusplus
54 extern "C"
55{
56# endif
57
58/* I don't recommend using this interface in general. Use `free'.
59 *
60 * I'm told Microsoft Windows may use one set of `malloc' and `free'
61 * in a library, and another incompatible set in a statically compiled
62 * application that link to the library, thus creating problems if the
63 * application would invoke `free' on a pointer pointing to memory
64 * allocated by the library. This motivated adding this function.
65 *
66 * The theory of isolating all memory allocations and de-allocations
67 * within a code package (library) sounds good, to simplify hunting
68 * down memory allocation related problems, but I'm not sure if it is
69 * worth enough to motivate recommending this interface over calling
70 * `free' directly, though.
71 *
72 * See the manual section 'Memory handling under Windows' for more
73 * information.
74 */
75
76 extern void IDNAPI idn_free (void *ptr);
77
78# ifdef __cplusplus
79}
80# endif
81
82#endif /* IDN_FREE_H */
idn_free
void IDNAPI idn_free(void *ptr)
Definition idn-free.c:52
IDNAPI
#define IDNAPI
Definition idn-free.h:49