00001 /* idn-free.h --- Invoke the `free' function releasing memory 00002 * allocated by libidn functions. 00003 * Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009 Simon Josefsson 00004 * 00005 * This file is part of GNU Libidn. 00006 * 00007 * GNU Libidn is free software; you can redistribute it and/or 00008 * modify it under the terms of the GNU Lesser General Public 00009 * License as published by the Free Software Foundation; either 00010 * version 2.1 of the License, or (at your option) any later version. 00011 * 00012 * GNU Libidn is distributed in the hope that it will be useful, 00013 * but WITHOUT ANY WARRANTY; without even the implied warranty of 00014 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU 00015 * Lesser General Public License for more details. 00016 * 00017 * You should have received a copy of the GNU Lesser General Public 00018 * License along with GNU Libidn; if not, write to the Free Software 00019 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA 00020 * 00021 */ 00022 00023 #ifndef IDN_FREE_H 00024 # define IDN_FREE_H 00025 00026 # ifndef IDNAPI 00027 # if defined LIBIDN_BUILDING && defined HAVE_VISIBILITY && HAVE_VISIBILITY 00028 # define IDNAPI __attribute__((__visibility__("default"))) 00029 # elif defined LIBIDN_BUILDING && defined _MSC_VER && ! defined LIBIDN_STATIC 00030 # define IDNAPI __declspec(dllexport) 00031 # elif defined _MSC_VER && ! defined LIBIDN_STATIC 00032 # define IDNAPI __declspec(dllimport) 00033 # else 00034 # define IDNAPI 00035 # endif 00036 # endif 00037 00038 /* I don't recommend using this interface in general. Use `free'. 00039 * 00040 * I'm told Microsoft Windows may use one set of `malloc' and `free' 00041 * in a library, and another incompatible set in a statically compiled 00042 * application that link to the library, thus creating problems if the 00043 * application would invoke `free' on a pointer pointing to memory 00044 * allocated by the library. This motivated adding this function. 00045 * 00046 * The theory of isolating all memory allocations and de-allocations 00047 * within a code package (library) sounds good, to simplify hunting 00048 * down memory allocation related problems, but I'm not sure if it is 00049 * worth enough to motivate recommending this interface over calling 00050 * `free' directly, though. 00051 * 00052 * See the manual section 'Memory handling under Windows' for more 00053 * information. 00054 */ 00055 00056 extern void IDNAPI idn_free (void *ptr); 00057 00058 #endif /* IDN_FREE_H */