08-21-2009
Quote:
Originally Posted by
Loic Domaigne
Do you mean <cstdio> ?
Yes, there is. Please check out the following link:
HTML Tidy: platform.h Source File
HTH,
Loïc
--
"There are two ways to write error-free programs; only the third one works." -- Alan J. Perlis
Yeah I meant <cstdio> sorry, I made a typo. Thanks for this it looks pretty interesting
3 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
We have a mix of AIX, HP-UX, Linux (RHEL and SLES), and Solaris in our environment. Currently we have seperate patch management systems for each platform (NIM, SD, Spacewalk, etc), but have started looking for a centralized patch management solution that would work for most, if not all, of our... (0 Replies)
Discussion started by: kknigga
0 Replies
2. Shell Programming and Scripting
Hi gurus, I am trying to match records in following format:
(-,username,domain1.co.uk)\
(-,username,domain2.co.uk)
either awk or perl must be used. I am using cygwin. I wrote following code which works and matches both above entries:
awk 'BEGIN {musr="(-,username,+.co.uk)"} {if... (8 Replies)
Discussion started by: wakatana
8 Replies
3. Solaris
Hi,
I have a multiprocess C application (used POSIX library for threads and fork() & exec for creating process) of millions of LOC.
1. Which works fine in single processor machine.
2. Which works fine in multicore machine only if one core is enabled.
Problem is, which results an undefined... (2 Replies)
Discussion started by: sreejesh
2 Replies
LEARN ABOUT FREEBSD
mac_free
MAC_FREE(3) BSD Library Functions Manual MAC_FREE(3)
NAME
mac_free -- free MAC label
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/mac.h>
int
mac_free(mac_t label);
DESCRIPTION
The mac_free() function frees the storage allocated to contain a mac_t.
RETURN VALUES
The mac_free() function always returns 0. WARNING: see the notes in the BUGS section regarding the use of this function.
SEE ALSO
mac(3), mac_get(3), mac_prepare(3), mac_set(3), mac_text(3), posix1e(3), mac(4), mac(9)
STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion of the draft continues on the cross-platform POSIX.1e implementation mailing
list. To join this list, see the FreeBSD POSIX.1e implementation page for more information.
HISTORY
Support for Mandatory Access Control was introduced in FreeBSD 5.0 as part of the TrustedBSD Project.
BUGS
POSIX.1e specifies that mac_free() will be used to free text strings created using mac_to_text(3). Because mac_t is a complex structure in
the TrustedBSD implementation, mac_free() is specific to mac_3, and must not be used to free the character strings returned from
mac_to_text(). Doing so may result in undefined behavior.
BSD
December 21, 2001 BSD