From: ziplock@yabbs To: htoaster@yabbs Subject: re: it works! Date: Sun Nov 14 12:44:27 1993 Have you looked at the sendmail 8 cdef's? I think it might just be one out of BSD4.4, but it's definitely recent. I think they use the same one for all the ports of sendmail 8. Does that create licence problems for you? /* * Copyright (c) 1991, 1993 *The Regents of the University of California. All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: *This product includes software developed by the University of *California, Berkeley and its contributors. * 4. Neither the name of the University nor the names of its contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * *@(#)cdefs.h8.2 (Berkeley) 10/4/93 */ #ifndef_CDEFS_H_ #define_CDEFS_H_ #if defined(__cplusplus) #define__BEGIN_DECLSextern "C" { #define__END_DECLS}; #else #define__BEGIN_DECLS #define__END_DECLS #endif /* * The __CONCAT macro is used to concatenate parts of symbol names, e.g. * with "#define OLD(foo) __CONCAT(old,foo)", OLD(foo) produces oldfoo. * The __CONCAT macro is a bit tricky -- make sure you don't put spaces * in between its arguments. __CONCAT can also concatenate double-quoted * strings produced by the __STRING macro, but this only works with ANSI C. */ #if defined(__STDC__) || defined(__cplusplus) #define__P(protos)protos/* full-blown ANSI C */ #define__CONCAT(x,y)x ## y #define__STRING(x)#x #if !defined(__GNUC__) && !defined(__cplusplus) #defineinline #endif #else/* !(__STDC__ || __cplusplus) */ #define__P(protos)()/* traditional C preprocessor */ #define__CONCAT(x,y)x/**/y #define__STRING(x)"x" #ifdef __GNUC__ #defineconst__const/* GCC: ANSI C with -traditional */ #defineinline__inline #definesigned__signed #definevolatile__volatile #else/* !__GNUC__ */ #defineconst/* delete ANSI C keywords */ #defineinline #definesigned #definevolatile #endif/* !__GNUC__ */ #endif/* !(__STDC__ || __cplusplus) */ /* * GCC has extensions for declaring functions as `pure' (always returns * the same value given the same inputs, i.e., has no external state and * no side effects) and `dead' (nonreturning). These mainly affect * optimization and warnings. Unfortunately, GCC complains if these are * used under strict ANSI mode (`gcc -ansi -pedantic'), hence we need to * define them only if compiling without this. */ #if defined(__GNUC__) && !defined(__STRICT_ANSI__) #define __dead __volatile #define __pure __const #else #define __dead #define __pure #endif #endif /* !_CDEFS_H_ */