Bug#729230: doxygen: hangs during ptlib build
Samuel Thibault
sthibault at debian.org
Sun Nov 10 17:58:35 UTC 2013
Control: tags -1 - moreinfo
Control: clone -1 -2
Control: reassign -2 ptlib
Control: retitle -2 FTBFS on doxygen call, please avoid doxygen known bug by dropping #operator>>
Control: found -2 2.10.10~dfsg-2
Control: fixed -2 2.12.7-1
Control: forcemerge -1 718694
Hello,
Helmut Grohne, le Sun 10 Nov 2013 18:19:05 +0100, a écrit :
> While it may be possible to reproduce the bug report using the
> information you sent, it is not useful. Neither me nor doko can sensibly
> do anything with bug reports such as this except for letting them rot.
> We have enough of them already.
Right. I too have hundreds of mails pending processing...
> Please include important information such as:
>
> * Which version of ptlib? Guess: 2.10.10~dfsg-2
Yes. 2.12.7-1 doesn't have the issue indeed.
> * Which architecture? Guess: amd64
Yes.
> * Invocation of doxygen
doxygen ptlib_cfg.dxy > doxygen.out
> * The Doxyfile
Attached, as well as the file it's stuck on.
> * Include a traceback. A doxygen-dbg package is about to hit NEW. So
> you don't even have to rebuild doxygen.
#0 __memset_sse2 () at ../sysdeps/x86_64/multiarch/../memset.S:335
#1 0x00002b76f7c1a07f in _int_malloc (av=0x2b76f7f44640 <main_arena>, bytes=32) at malloc.c:3741
#2 0x00002b76f7c1c093 in __GI___libc_malloc (bytes=32) at malloc.c:2859
#3 0x00002b76f73e5e6d in operator new(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4 0x00000000007147c1 in QString::QString (this=0x7fffc9c8cd30, ch=...) at qstring.cpp:12233
#5 0x000000000071557e in QString::findRev (this=this at entry=0x7fffc9c8cec0, c=..., index=index at entry=-2, cs=cs at entry=true) at qstring.cpp:13020
#6 0x00000000005d8780 in findRev (cs=true, index=-2, c=60 '<', this=0x7fffc9c8cec0) at ../qtools/qstring.h:736
#7 findParameterList (name=...) at util.cpp:1840
#8 0x00000000005eedbc in resolveRef (scName=0x64fc500 "PObject", name=0x64fdd70 "#operator>>", inSeeBlock=<optimized out>, resContext=resContext at entry=0x7fffc9c8cf90,
resMember=resMember at entry=0x7fffc9c8cf98, lookForSpecialization=lookForSpecialization at entry=true, currentFile=0x2a962c0, checkScope=checkScope at entry=true) at util.cpp:4363
#9 0x0000000000687130 in handleLinkedWord (parent=parent at entry=0x64fdd20, children=...) at docparser.cpp:1030
#10 0x000000000068fe4b in DocPara::parse (this=this at entry=0x64fdce0) at docparser.cpp:6311
#11 0x0000000000698599 in DocRoot::parse (this=this at entry=0x64fdc80) at docparser.cpp:6843
#12 0x0000000000698c0c in validatingParseDoc (fileName=fileName at entry=0x64fd8b0 "/tmp/ptlib-2.10.10~dfsg/include/ptlib/object.h", startLine=startLine at entry=1294, ctx=ctx at entry=
0x2ae6390, md=md at entry=0x3b094c0,
input=0x64fce30 " The exact input is\ndependent on the exact semantics of the descendent class. This is\nprimarily used by the standard <code>#operator>></code> function.\n\nThe default behaviour is to do nothing.\n", indexWords=indexWords at entry=true, isExample=isExample at entry=false, exampleName=exampleName at entry=0x0, singleLine=false,
linkFromIndex=linkFromIndex at entry=false) at docparser.cpp:7085
#13 0x000000000056df4a in OutputList::generateDoc (this=this at entry=0x3083440, fileName=0x64fd8b0 "/tmp/ptlib-2.10.10~dfsg/include/ptlib/object.h", startLine=startLine at entry=1294,
ctx=ctx at entry=0x2ae6390, md=md at entry=0x3b094c0, docStr=..., indexWords=indexWords at entry=true, isExample=isExample at entry=false, exampleName=exampleName at entry=0x0,
singleLine=singleLine at entry=false, linkFromIndex=linkFromIndex at entry=false) at outputlist.cpp:153
#14 0x000000000055cb2c in MemberDef::writeDocumentation (this=0x3b094c0, ml=ml at entry=0x3affaf0, ol=..., scName=scName at entry=0x64fd780 "PObject",
container=container at entry=0x2ae6390, inGroup=<optimized out>, showEnumValues=showEnumValues at entry=false, showInline=showInline at entry=false) at memberdef.cpp:2745
---Type <return> to continue, or q <return> to quit---
#15 0x000000000056413f in MemberList::writeDocumentation (this=this at entry=0x3affaf0, ol=..., scopeName=0x64fd780 "PObject", container=container at entry=0x2ae6390,
title=title at entry=0x64fd1b0 "Member Function Documentation", showEnumValues=showEnumValues at entry=false, showInline=showInline at entry=false) at memberlist.cpp:655
#16 0x00000000006396ce in ClassDef::writeMemberDocumentation (this=this at entry=0x2ae6390, ol=..., lt=<optimized out>, title=..., showInline=showInline at entry=false)
at classdef.cpp:4269
#17 0x000000000063bb5e in ClassDef::writeDocumentationContents (this=this at entry=0x2ae6390, ol=...) at classdef.cpp:1944
#18 0x000000000063bf54 in ClassDef::writeDocumentation (this=this at entry=0x2ae6390, ol=...) at classdef.cpp:2046
#19 0x000000000040ea4c in generateClassList (classSDict=...) at doxygen.cpp:7993
#20 0x00000000004310bb in generateClassDocs () at doxygen.cpp:8004
#21 generateOutput () at doxygen.cpp:11243
#22 0x000000000040960e in main (argc=2, argv=0x7fffc9c8d8f8) at main.cpp:38
It's indeed findParameterList which doesn't return:
(gdb) c
Run till exit from #0 findParameterList (name=...) at util.cpp:1841
hangs
> * Check for duplicates, especially #718694
Most probably a duplicate then, indeed, I failed to find it among the
open bugs. Removing <code>#operator>></code> in the header does fix the
issue. Cloning as a bug against ptlib and merging with the duplicate.
Samuel
-------------- next part --------------
# Doxyfile 1.6.1
# This file describes the settings to be used by the documentation system
# doxygen (www.doxygen.org) for a project
#
# All text after a hash (#) is considered a comment and will be ignored
# The format is:
# TAG = value [value, ...]
# For lists items can also be appended using:
# TAG += value [value, ...]
# Values that contain spaces should be placed between quotes (" ")
#---------------------------------------------------------------------------
# Project related configuration options
#---------------------------------------------------------------------------
# This tag specifies the encoding used for all characters in the config file
# that follow. The default is UTF-8 which is also the encoding used for all
# text before the first occurrence of this tag. Doxygen uses libiconv (or the
# iconv built into libc) for the transcoding. See
# http://www.gnu.org/software/libiconv for the list of possible encodings.
DOXYFILE_ENCODING = UTF-8
# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
# by quotes) that should identify the project.
PROJECT_NAME = PTLib
# The PROJECT_NUMBER tag can be used to enter a project or revision number.
# This could be handy for archiving the generated documentation or
# if some version control system is used.
PROJECT_NUMBER = Version 2.10.10
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
# base path where the generated documentation will be put.
# If a relative path is entered, it will be relative to the location
# where doxygen was started. If left blank the current directory will be used.
OUTPUT_DIRECTORY = .
# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
# 4096 sub-directories (in 2 levels) under the output directory of each output
# format and will distribute the generated files over these directories.
# Enabling this option can be useful when feeding doxygen a huge amount of
# source files, where putting all generated files in the same directory would
# otherwise cause performance problems for the file system.
CREATE_SUBDIRS = YES
# The OUTPUT_LANGUAGE tag is used to specify the language in which all
# documentation generated by doxygen is written. Doxygen will use this
# information to generate all constant output in the proper language.
# The default language is English, other supported languages are:
# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak,
# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
OUTPUT_LANGUAGE = English
# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
# include brief member descriptions after the members that are listed in
# the file and class documentation (similar to JavaDoc).
# Set to NO to disable this.
BRIEF_MEMBER_DESC = YES
# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
# the brief description of a member or function before the detailed description.
# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
# brief descriptions will be completely suppressed.
REPEAT_BRIEF = YES
# This tag implements a quasi-intelligent brief description abbreviator
# that is used to form the text in various listings. Each string
# in this list, if found as the leading text of the brief description, will be
# stripped from the text and the result after processing the whole list, is
# used as the annotated text. Otherwise, the brief description is used as-is.
# If left blank, the following values are used ("$name" is automatically
# replaced with the name of the entity): "The $name class" "The $name widget"
# "The $name file" "is" "provides" "specifies" "contains"
# "represents" "a" "an" "the"
ABBREVIATE_BRIEF =
# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
# Doxygen will generate a detailed section even if there is only a brief
# description.
ALWAYS_DETAILED_SEC = YES
# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
# inherited members of a class in the documentation of that class as if those
# members were ordinary class members. Constructors, destructors and assignment
# operators of the base classes will not be shown.
INLINE_INHERITED_MEMB = NO
# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
# path before files name in the file list and in the header files. If set
# to NO the shortest path that makes the file name unique will be used.
FULL_PATH_NAMES = NO
# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
# can be used to strip a user-defined part of the path. Stripping is
# only done if one of the specified strings matches the left-hand part of
# the path. The tag can be used to show relative paths in the file list.
# If left blank the directory from which doxygen is run is used as the
# path to strip.
STRIP_FROM_PATH =
# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
# the path mentioned in the documentation of a class, which tells
# the reader which header file to include in order to use a class.
# If left blank only the name of the header file containing the class
# definition is used. Otherwise one should specify the include paths that
# are normally passed to the compiler using the -I flag.
STRIP_FROM_INC_PATH =
# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
# (but less readable) file names. This can be useful is your file systems
# doesn't support long names like on DOS, Mac, or CD-ROM.
SHORT_NAMES = NO
# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
# will interpret the first line (until the first dot) of a JavaDoc-style
# comment as the brief description. If set to NO, the JavaDoc
# comments will behave just like regular Qt-style comments
# (thus requiring an explicit @brief command for a brief description.)
JAVADOC_AUTOBRIEF = YES
# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
# interpret the first line (until the first dot) of a Qt-style
# comment as the brief description. If set to NO, the comments
# will behave just like regular Qt-style comments (thus requiring
# an explicit \brief command for a brief description.)
QT_AUTOBRIEF = YES
# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
# treat a multi-line C++ special comment block (i.e. a block of //! or ///
# comments) as a brief description. This used to be the default behaviour.
# The new default is to treat a multi-line C++ comment block as a detailed
# description. Set this tag to YES if you prefer the old behaviour instead.
MULTILINE_CPP_IS_BRIEF = NO
# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
# member inherits the documentation from any documented member that it
# re-implements.
INHERIT_DOCS = YES
# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
# a new page for each member. If set to NO, the documentation of a member will
# be part of the file/class/namespace that contains it.
SEPARATE_MEMBER_PAGES = NO
# The TAB_SIZE tag can be used to set the number of spaces in a tab.
# Doxygen uses this value to replace tabs by spaces in code fragments.
TAB_SIZE = 8
# This tag can be used to specify a number of aliases that acts
# as commands in the documentation. An alias has the form "name=value".
# For example adding "sideeffect=\par Side Effects:\n" will allow you to
# put the command \sideeffect (or @sideeffect) in the documentation, which
# will result in a user-defined paragraph with heading "Side Effects:".
# You can put \n's in the value part of an alias to insert newlines.
ALIASES =
# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
# sources only. Doxygen will then generate output that is more tailored for C.
# For instance, some of the names that are used will be different. The list
# of all members will be omitted, etc.
OPTIMIZE_OUTPUT_FOR_C = NO
# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
# sources only. Doxygen will then generate output that is more tailored for
# Java. For instance, namespaces will be presented as packages, qualified
# scopes will look different, etc.
OPTIMIZE_OUTPUT_JAVA = NO
# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
# sources only. Doxygen will then generate output that is more tailored for
# Fortran.
OPTIMIZE_FOR_FORTRAN = NO
# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
# sources. Doxygen will then generate output that is tailored for
# VHDL.
OPTIMIZE_OUTPUT_VHDL = NO
# Doxygen selects the parser to use depending on the extension of the files it parses.
# With this tag you can assign which parser to use for a given extension.
# Doxygen has a built-in mapping, but you can override or extend it using this tag.
# The format is ext=language, where ext is a file extension, and language is one of
# the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP,
# Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat
# .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran),
# use: inc=Fortran f=C. Note that for custom extensions you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
EXTENSION_MAPPING =
# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
# to include (a tag file for) the STL sources as input, then you should
# set this tag to YES in order to let doxygen match functions declarations and
# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
# func(std::string) {}). This also make the inheritance and collaboration
# diagrams that involve STL classes more complete and accurate.
BUILTIN_STL_SUPPORT = YES
# If you use Microsoft's C++/CLI language, you should set this option to YES to
# enable parsing support.
CPP_CLI_SUPPORT = NO
# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
# Doxygen will parse them like normal C++ but will assume all classes use public
# instead of private inheritance when no explicit protection keyword is present.
SIP_SUPPORT = NO
# For Microsoft's IDL there are propget and propput attributes to indicate getter
# and setter methods for a property. Setting this option to YES (the default)
# will make doxygen to replace the get and set methods by a property in the
# documentation. This will only work if the methods are indeed getting or
# setting a simple type. If this is not the case, or you want to show the
# methods anyway, you should set this option to NO.
IDL_PROPERTY_SUPPORT = YES
# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
# tag is set to YES, then doxygen will reuse the documentation of the first
# member in the group (if any) for the other members of the group. By default
# all members of a group must be documented explicitly.
DISTRIBUTE_GROUP_DOC = NO
# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
# the same type (for instance a group of public functions) to be put as a
# subgroup of that type (e.g. under the Public Functions section). Set it to
# NO to prevent subgrouping. Alternatively, this can be done per class using
# the \nosubgrouping command.
SUBGROUPING = YES
# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
# is documented as struct, union, or enum with the name of the typedef. So
# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
# with name TypeT. When disabled the typedef will appear as a member of a file,
# namespace, or class. And the struct will be named TypeS. This can typically
# be useful for C code in case the coding convention dictates that all compound
# types are typedef'ed and only the typedef is referenced, never the tag name.
TYPEDEF_HIDES_STRUCT = YES
# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
# determine which symbols to keep in memory and which to flush to disk.
# When the cache is full, less often used symbols will be written to disk.
# For small to medium size projects (<1000 input files) the default value is
# probably good enough. For larger projects a too small cache size can cause
# doxygen to be busy swapping symbols to and from disk most of the time
# causing a significant performance penality.
# If the system has enough physical memory increasing the cache will improve the
# performance by keeping more symbols in memory. Note that the value works on
# a logarithmic scale so increasing the size by one will rougly double the
# memory usage. The cache size is given by this formula:
# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
# corresponding to a cache size of 2^16 = 65536 symbols
SYMBOL_CACHE_SIZE = 0
#---------------------------------------------------------------------------
# Build related configuration options
#---------------------------------------------------------------------------
# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
# documentation are documented, even if no documentation was available.
# Private class members and static file members will be hidden unless
# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
EXTRACT_ALL = YES
# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
# will be included in the documentation.
EXTRACT_PRIVATE = NO
# If the EXTRACT_STATIC tag is set to YES all static members of a file
# will be included in the documentation.
EXTRACT_STATIC = YES
# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
# defined locally in source files will be included in the documentation.
# If set to NO only classes defined in header files are included.
EXTRACT_LOCAL_CLASSES = NO
# This flag is only useful for Objective-C code. When set to YES local
# methods, which are defined in the implementation section but not in
# the interface are included in the documentation.
# If set to NO (the default) only methods in the interface are included.
EXTRACT_LOCAL_METHODS = NO
# If this flag is set to YES, the members of anonymous namespaces will be
# extracted and appear in the documentation as a namespace called
# 'anonymous_namespace{file}', where file will be replaced with the base
# name of the file that contains the anonymous namespace. By default
# anonymous namespace are hidden.
EXTRACT_ANON_NSPACES = NO
# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
# undocumented members of documented classes, files or namespaces.
# If set to NO (the default) these members will be included in the
# various overviews, but no documentation section is generated.
# This option has no effect if EXTRACT_ALL is enabled.
HIDE_UNDOC_MEMBERS = NO
# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
# undocumented classes that are normally visible in the class hierarchy.
# If set to NO (the default) these classes will be included in the various
# overviews. This option has no effect if EXTRACT_ALL is enabled.
HIDE_UNDOC_CLASSES = YES
# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
# friend (class|struct|union) declarations.
# If set to NO (the default) these declarations will be included in the
# documentation.
HIDE_FRIEND_COMPOUNDS = YES
# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
# documentation blocks found inside the body of a function.
# If set to NO (the default) these blocks will be appended to the
# function's detailed documentation block.
HIDE_IN_BODY_DOCS = NO
# The INTERNAL_DOCS tag determines if documentation
# that is typed after a \internal command is included. If the tag is set
# to NO (the default) then the documentation will be excluded.
# Set it to YES to include the internal documentation.
INTERNAL_DOCS = NO
# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
# file names in lower-case letters. If set to YES upper-case letters are also
# allowed. This is useful if you have classes or files whose names only differ
# in case and if your file system supports case sensitive file names. Windows
# and Mac users are advised to set this option to NO.
CASE_SENSE_NAMES = YES
# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
# will show members with their full class and namespace scopes in the
# documentation. If set to YES the scope will be hidden.
HIDE_SCOPE_NAMES = NO
# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
# will put a list of the files that are included by a file in the documentation
# of that file.
SHOW_INCLUDE_FILES = YES
# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
# is inserted in the documentation for inline members.
INLINE_INFO = YES
# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
# will sort the (detailed) documentation of file and class members
# alphabetically by member name. If set to NO the members will appear in
# declaration order.
SORT_MEMBER_DOCS = YES
# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
# brief documentation of file, namespace and class members alphabetically
# by member name. If set to NO (the default) the members will appear in
# declaration order.
SORT_BRIEF_DOCS = NO
# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the (brief and detailed) documentation of class members so that constructors and destructors are listed first. If set to NO (the default) the constructors will appear in the respective orders defined by SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
SORT_MEMBERS_CTORS_1ST = NO
# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
# hierarchy of group names into alphabetical order. If set to NO (the default)
# the group names will appear in their defined order.
SORT_GROUP_NAMES = NO
# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
# sorted by fully-qualified names, including namespaces. If set to
# NO (the default), the class list will be sorted only by class name,
# not including the namespace part.
# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
# Note: This option applies only to the class list, not to the
# alphabetical list.
SORT_BY_SCOPE_NAME = YES
# The GENERATE_TODOLIST tag can be used to enable (YES) or
# disable (NO) the todo list. This list is created by putting \todo
# commands in the documentation.
GENERATE_TODOLIST = YES
# The GENERATE_TESTLIST tag can be used to enable (YES) or
# disable (NO) the test list. This list is created by putting \test
# commands in the documentation.
GENERATE_TESTLIST = YES
# The GENERATE_BUGLIST tag can be used to enable (YES) or
# disable (NO) the bug list. This list is created by putting \bug
# commands in the documentation.
GENERATE_BUGLIST = YES
# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
# disable (NO) the deprecated list. This list is created by putting
# \deprecated commands in the documentation.
GENERATE_DEPRECATEDLIST= YES
# The ENABLED_SECTIONS tag can be used to enable conditional
# documentation sections, marked by \if sectionname ... \endif.
ENABLED_SECTIONS =
# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
# the initial value of a variable or define consists of for it to appear in
# the documentation. If the initializer consists of more lines than specified
# here it will be hidden. Use a value of 0 to hide initializers completely.
# The appearance of the initializer of individual variables and defines in the
# documentation can be controlled using \showinitializer or \hideinitializer
# command in the documentation regardless of this setting.
MAX_INITIALIZER_LINES = 30
# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
# at the bottom of the documentation of classes and structs. If set to YES the
# list will mention the files that were used to generate the documentation.
SHOW_USED_FILES = YES
# If the sources in your project are distributed over multiple directories
# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
# in the documentation. The default is NO.
SHOW_DIRECTORIES = YES
# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
# This will remove the Files entry from the Quick Index and from the
# Folder Tree View (if specified). The default is YES.
SHOW_FILES = YES
# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
# Namespaces page.
# This will remove the Namespaces entry from the Quick Index
# and from the Folder Tree View (if specified). The default is YES.
SHOW_NAMESPACES = YES
# The FILE_VERSION_FILTER tag can be used to specify a program or script that
# doxygen should invoke to get the current version for each file (typically from
# the version control system). Doxygen will invoke the program by executing (via
# popen()) the command <command> <input-file>, where <command> is the value of
# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
# provided by doxygen. Whatever the program writes to standard output
# is used as the file version. See the manual for examples.
FILE_VERSION_FILTER =
# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by
# doxygen. The layout file controls the global structure of the generated output files
# in an output format independent way. The create the layout file that represents
# doxygen's defaults, run doxygen with the -l option. You can optionally specify a
# file name after the option, if omitted DoxygenLayout.xml will be used as the name
# of the layout file.
LAYOUT_FILE =
#---------------------------------------------------------------------------
# configuration options related to warning and progress messages
#---------------------------------------------------------------------------
# The QUIET tag can be used to turn on/off the messages that are generated
# by doxygen. Possible values are YES and NO. If left blank NO is used.
QUIET = NO
# The WARNINGS tag can be used to turn on/off the warning messages that are
# generated by doxygen. Possible values are YES and NO. If left blank
# NO is used.
WARNINGS = YES
# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
# automatically be disabled.
WARN_IF_UNDOCUMENTED = YES
# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
# potential errors in the documentation, such as not documenting some
# parameters in a documented function, or documenting parameters that
# don't exist or using markup commands wrongly.
WARN_IF_DOC_ERROR = YES
# This WARN_NO_PARAMDOC option can be abled to get warnings for
# functions that are documented, but have no documentation for their parameters
# or return value. If set to NO (the default) doxygen will only warn about
# wrong or incomplete parameter documentation, but not about the absence of
# documentation.
WARN_NO_PARAMDOC = NO
# The WARN_FORMAT tag determines the format of the warning messages that
# doxygen can produce. The string should contain the $file, $line, and $text
# tags, which will be replaced by the file and line number from which the
# warning originated and the warning text. Optionally the format may contain
# $version, which will be replaced by the version of the file (if it could
# be obtained via FILE_VERSION_FILTER)
WARN_FORMAT = "$file:$line: $text"
# The WARN_LOGFILE tag can be used to specify a file to which warning
# and error messages should be written. If left blank the output is written
# to stderr.
WARN_LOGFILE =
#---------------------------------------------------------------------------
# configuration options related to the input files
#---------------------------------------------------------------------------
# The INPUT tag can be used to specify the files and/or directories that contain
# documented source files. You may enter file names like "myfile.cpp" or
# directories like "/usr/src/myproject". Separate the files or directories
# with spaces.
INPUT = ./ptlib.dxy \
./include/ptlib \
./include/ptclib
# This tag can be used to specify the character encoding of the source files
# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
# also the default input encoding. Doxygen uses libiconv (or the iconv built
# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
# the list of possible encodings.
INPUT_ENCODING = UTF-8
# If the value of the INPUT tag contains directories, you can use the
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
# and *.h) to filter out the source-files in the directories. If left
# blank the following patterns are tested:
# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
FILE_PATTERNS = *.h
# The RECURSIVE tag can be used to turn specify whether or not subdirectories
# should be searched for input files as well. Possible values are YES and NO.
# If left blank NO is used.
RECURSIVE = NO
# The EXCLUDE tag can be used to specify files and/or directories that should
# excluded from the INPUT source files. This way you can easily exclude a
# subdirectory from a directory tree whose root is specified with the INPUT tag.
EXCLUDE = videoio1394dc.h
# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
# directories that are symbolic links (a Unix filesystem feature) are excluded
# from the input.
EXCLUDE_SYMLINKS = NO
# If the value of the INPUT tag contains directories, you can use the
# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
# certain files from those directories. Note that the wildcards are matched
# against the file with absolute path, so to exclude all test directories
# for example use the pattern */test/*
EXCLUDE_PATTERNS =
# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
# (namespaces, classes, functions, etc.) that should be excluded from the
# output. The symbol name can be a fully qualified name, a word, or if the
# wildcard * is used, a substring. Examples: ANamespace, AClass,
# AClass::ANamespace, ANamespace::*Test
EXCLUDE_SYMBOLS =
# The EXAMPLE_PATH tag can be used to specify one or more files or
# directories that contain example code fragments that are included (see
# the \include command).
EXAMPLE_PATH =
# If the value of the EXAMPLE_PATH tag contains directories, you can use the
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
# and *.h) to filter out the source-files in the directories. If left
# blank all files are included.
EXAMPLE_PATTERNS =
# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
# searched for input files to be used with the \include or \dontinclude
# commands irrespective of the value of the RECURSIVE tag.
# Possible values are YES and NO. If left blank NO is used.
EXAMPLE_RECURSIVE = NO
# The IMAGE_PATH tag can be used to specify one or more files or
# directories that contain image that are included in the documentation (see
# the \image command).
IMAGE_PATH =
# The INPUT_FILTER tag can be used to specify a program that doxygen should
# invoke to filter for each input file. Doxygen will invoke the filter program
# by executing (via popen()) the command <filter> <input-file>, where <filter>
# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
# input file. Doxygen will then use the output that the filter program writes
# to standard output.
# If FILTER_PATTERNS is specified, this tag will be
# ignored.
INPUT_FILTER =
# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
# basis.
# Doxygen will compare the file name with each pattern and apply the
# filter if there is a match.
# The filters are a list of the form:
# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
# is applied to all files.
FILTER_PATTERNS =
# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
# INPUT_FILTER) will be used to filter the input files when producing source
# files to browse (i.e. when SOURCE_BROWSER is set to YES).
FILTER_SOURCE_FILES = NO
#---------------------------------------------------------------------------
# configuration options related to source browsing
#---------------------------------------------------------------------------
# If the SOURCE_BROWSER tag is set to YES then a list of source files will
# be generated. Documented entities will be cross-referenced with these sources.
# Note: To get rid of all source code in the generated output, make sure also
# VERBATIM_HEADERS is set to NO.
SOURCE_BROWSER = NO
# Setting the INLINE_SOURCES tag to YES will include the body
# of functions and classes directly in the documentation.
INLINE_SOURCES = NO
# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
# doxygen to hide any special comment blocks from generated source code
# fragments. Normal C and C++ comments will always remain visible.
STRIP_CODE_COMMENTS = YES
# If the REFERENCED_BY_RELATION tag is set to YES
# then for each documented function all documented
# functions referencing it will be listed.
REFERENCED_BY_RELATION = YES
# If the REFERENCES_RELATION tag is set to YES
# then for each documented function all documented entities
# called/used by that function will be listed.
REFERENCES_RELATION = YES
# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
# link to the source code.
# Otherwise they will link to the documentation.
REFERENCES_LINK_SOURCE = YES
# If the USE_HTAGS tag is set to YES then the references to source code
# will point to the HTML generated by the htags(1) tool instead of doxygen
# built-in source browser. The htags tool is part of GNU's global source
# tagging system (see http://www.gnu.org/software/global/global.html). You
# will need version 4.8.6 or higher.
USE_HTAGS = NO
# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
# will generate a verbatim copy of the header file for each class for
# which an include is specified. Set to NO to disable this.
VERBATIM_HEADERS = YES
#---------------------------------------------------------------------------
# configuration options related to the alphabetical class index
#---------------------------------------------------------------------------
# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
# of all compounds will be generated. Enable this if the project
# contains a lot of classes, structs, unions or interfaces.
ALPHABETICAL_INDEX = YES
# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
# in which this list will be split (can be a number in the range [1..20])
COLS_IN_ALPHA_INDEX = 5
# In case all classes in a project start with a common prefix, all
# classes will be put under the same header in the alphabetical index.
# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
# should be ignored while generating the index headers.
IGNORE_PREFIX =
#---------------------------------------------------------------------------
# configuration options related to the HTML output
#---------------------------------------------------------------------------
# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
# generate HTML output.
GENERATE_HTML = YES
# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `html' will be used as the default path.
HTML_OUTPUT = html
# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
# doxygen will generate files with .html extension.
HTML_FILE_EXTENSION = .html
# The HTML_HEADER tag can be used to specify a personal HTML header for
# each generated HTML page. If it is left blank doxygen will generate a
# standard header.
HTML_HEADER =
# The HTML_FOOTER tag can be used to specify a personal HTML footer for
# each generated HTML page. If it is left blank doxygen will generate a
# standard footer.
HTML_FOOTER =
# If the HTML_TIMESTAMP tag is set to YES then the generated HTML
# documentation will contain the timesstamp.
HTML_TIMESTAMP = YES
# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
# style sheet that is used by each HTML page. It can be used to
# fine-tune the look of the HTML output. If the tag is left blank doxygen
# will generate a default style sheet. Note that doxygen will try to copy
# the style sheet file to the HTML output directory, so don't put your own
# stylesheet in the HTML output directory as well, or it will be erased!
HTML_STYLESHEET =
# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
# files or namespaces will be aligned in HTML using tables. If set to
# NO a bullet list will be used.
HTML_ALIGN_MEMBERS = YES
# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
# documentation will contain sections that can be hidden and shown after the
# page has loaded. For this to work a browser that supports
# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
HTML_DYNAMIC_SECTIONS = NO
# If the GENERATE_DOCSET tag is set to YES, additional index files
# will be generated that can be used as input for Apple's Xcode 3
# integrated development environment, introduced with OSX 10.5 (Leopard).
# To create a documentation set, doxygen will generate a Makefile in the
# HTML output directory. Running make will produce the docset in that
# directory and running "make install" will install the docset in
# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
# it at startup.
# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.
GENERATE_DOCSET = NO
# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
# feed. A documentation feed provides an umbrella under which multiple
# documentation sets from a single provider (such as a company or product suite)
# can be grouped.
DOCSET_FEEDNAME = "Doxygen generated docs"
# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
# should uniquely identify the documentation set bundle. This should be a
# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
# will append .docset to the name.
DOCSET_BUNDLE_ID = org.doxygen.Project
# If the GENERATE_HTMLHELP tag is set to YES, additional index files
# will be generated that can be used as input for tools like the
# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
# of the generated HTML documentation.
GENERATE_HTMLHELP = NO
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
# be used to specify the file name of the resulting .chm file. You
# can add a path in front of the file if the result should not be
# written to the html output directory.
CHM_FILE =
# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
# be used to specify the location (absolute path including file name) of
# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
# the HTML help compiler on the generated index.hhp.
HHC_LOCATION =
# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
# controls if a separate .chi index file is generated (YES) or that
# it should be included in the master .chm file (NO).
GENERATE_CHI = NO
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
# is used to encode HtmlHelp index (hhk), content (hhc) and project file
# content.
CHM_INDEX_ENCODING =
# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
# controls whether a binary table of contents is generated (YES) or a
# normal table of contents (NO) in the .chm file.
BINARY_TOC = NO
# The TOC_EXPAND flag can be set to YES to add extra items for group members
# to the contents of the HTML help documentation and to the tree view.
TOC_EXPAND = NO
# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER
# are set, an additional index file will be generated that can be used as input for
# Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated
# HTML documentation.
GENERATE_QHP = NO
# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
# be used to specify the file name of the resulting .qch file.
# The path specified is relative to the HTML output folder.
QCH_FILE =
# The QHP_NAMESPACE tag specifies the namespace to use when generating
# Qt Help Project output. For more information please see
# http://doc.trolltech.com/qthelpproject.html#namespace
QHP_NAMESPACE =
# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
# Qt Help Project output. For more information please see
# http://doc.trolltech.com/qthelpproject.html#virtual-folders
QHP_VIRTUAL_FOLDER = doc
# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add.
# For more information please see
# http://doc.trolltech.com/qthelpproject.html#custom-filters
QHP_CUST_FILTER_NAME =
# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see
# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.
QHP_CUST_FILTER_ATTRS =
# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's
# filter section matches.
# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.
QHP_SECT_FILTER_ATTRS =
# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
# be used to specify the location of Qt's qhelpgenerator.
# If non-empty doxygen will try to run qhelpgenerator on the generated
# .qhp file.
QHG_LOCATION =
# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
# top of each HTML page. The value NO (the default) enables the index and
# the value YES disables it.
DISABLE_INDEX = NO
# This tag can be used to set the number of enum values (range [1..20])
# that doxygen will group on one line in the generated HTML documentation.
ENUM_VALUES_PER_LINE = 4
# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
# structure should be generated to display hierarchical information.
# If the tag value is set to YES, a side panel will be generated
# containing a tree-like index structure (just like the one that
# is generated for HTML Help). For this to work a browser that supports
# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
# Windows users are probably better off using the HTML help feature.
GENERATE_TREEVIEW = YES
# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
# and Class Hierarchy pages using a tree view instead of an ordered list.
USE_INLINE_TREES = NO
# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
# used to set the initial width (in pixels) of the frame in which the tree
# is shown.
TREEVIEW_WIDTH = 250
# Use this tag to change the font size of Latex formulas included
# as images in the HTML documentation. The default is 10. Note that
# when you change the font size after a successful doxygen run you need
# to manually remove any form_*.png images from the HTML output directory
# to force them to be regenerated.
FORMULA_FONTSIZE = 10
# When the SEARCHENGINE tag is enable doxygen will generate a search box for the HTML output. The underlying search engine uses javascript
# and DHTML and should work on any modern browser. Note that when using HTML help (GENERATE_HTMLHELP) or Qt help (GENERATE_QHP)
# there is already a search function so this one should typically
# be disabled.
SEARCHENGINE = YES
#---------------------------------------------------------------------------
# configuration options related to the LaTeX output
#---------------------------------------------------------------------------
# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
# generate Latex output.
GENERATE_LATEX = NO
# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `latex' will be used as the default path.
LATEX_OUTPUT = latex
# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
# invoked. If left blank `latex' will be used as the default command name.
LATEX_CMD_NAME = latex
# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
# generate index for LaTeX. If left blank `makeindex' will be used as the
# default command name.
MAKEINDEX_CMD_NAME = makeindex
# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
# LaTeX documents. This may be useful for small projects and may help to
# save some trees in general.
COMPACT_LATEX = NO
# The PAPER_TYPE tag can be used to set the paper type that is used
# by the printer. Possible values are: a4, a4wide, letter, legal and
# executive. If left blank a4wide will be used.
PAPER_TYPE = a4wide
# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
# packages that should be included in the LaTeX output.
EXTRA_PACKAGES =
# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
# the generated latex document. The header should contain everything until
# the first chapter. If it is left blank doxygen will generate a
# standard header. Notice: only use this tag if you know what you are doing!
LATEX_HEADER =
# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
# is prepared for conversion to pdf (using ps2pdf). The pdf file will
# contain links (just like the HTML output) instead of page references
# This makes the output suitable for online browsing using a pdf viewer.
PDF_HYPERLINKS = NO
# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
# plain latex in the generated Makefile. Set this option to YES to get a
# higher quality PDF documentation.
USE_PDFLATEX = NO
# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
# command to the generated LaTeX files. This will instruct LaTeX to keep
# running if errors occur, instead of asking the user for help.
# This option is also used when generating formulas in HTML.
LATEX_BATCHMODE = NO
# If LATEX_HIDE_INDICES is set to YES then doxygen will not
# include the index chapters (such as File Index, Compound Index, etc.)
# in the output.
LATEX_HIDE_INDICES = NO
# If LATEX_SOURCE_CODE is set to YES then doxygen will include source code with syntax highlighting in the LaTeX output. Note that which sources are shown also depends on other settings such as SOURCE_BROWSER.
LATEX_SOURCE_CODE = NO
#---------------------------------------------------------------------------
# configuration options related to the RTF output
#---------------------------------------------------------------------------
# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
# The RTF output is optimized for Word 97 and may not look very pretty with
# other RTF readers or editors.
GENERATE_RTF = NO
# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `rtf' will be used as the default path.
RTF_OUTPUT = rtf
# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
# RTF documents. This may be useful for small projects and may help to
# save some trees in general.
COMPACT_RTF = NO
# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
# will contain hyperlink fields. The RTF file will
# contain links (just like the HTML output) instead of page references.
# This makes the output suitable for online browsing using WORD or other
# programs which support those fields.
# Note: wordpad (write) and others do not support links.
RTF_HYPERLINKS = NO
# Load stylesheet definitions from file. Syntax is similar to doxygen's
# config file, i.e. a series of assignments. You only have to provide
# replacements, missing definitions are set to their default value.
RTF_STYLESHEET_FILE =
# Set optional variables used in the generation of an rtf document.
# Syntax is similar to doxygen's config file.
RTF_EXTENSIONS_FILE =
#---------------------------------------------------------------------------
# configuration options related to the man page output
#---------------------------------------------------------------------------
# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
# generate man pages
GENERATE_MAN = NO
# The MAN_OUTPUT tag is used to specify where the man pages will be put.
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `man' will be used as the default path.
MAN_OUTPUT = man
# The MAN_EXTENSION tag determines the extension that is added to
# the generated man pages (default is the subroutine's section .3)
MAN_EXTENSION = .3
# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
# then it will generate one additional man file for each entity
# documented in the real man page(s). These additional files
# only source the real man page, but without them the man command
# would be unable to find the correct page. The default is NO.
MAN_LINKS = NO
#---------------------------------------------------------------------------
# configuration options related to the XML output
#---------------------------------------------------------------------------
# If the GENERATE_XML tag is set to YES Doxygen will
# generate an XML file that captures the structure of
# the code including all documentation.
GENERATE_XML = NO
# The XML_OUTPUT tag is used to specify where the XML pages will be put.
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `xml' will be used as the default path.
XML_OUTPUT = xml
# The XML_SCHEMA tag can be used to specify an XML schema,
# which can be used by a validating XML parser to check the
# syntax of the XML files.
XML_SCHEMA =
# The XML_DTD tag can be used to specify an XML DTD,
# which can be used by a validating XML parser to check the
# syntax of the XML files.
XML_DTD =
# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
# dump the program listings (including syntax highlighting
# and cross-referencing information) to the XML output. Note that
# enabling this will significantly increase the size of the XML output.
XML_PROGRAMLISTING = YES
#---------------------------------------------------------------------------
# configuration options for the AutoGen Definitions output
#---------------------------------------------------------------------------
# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
# generate an AutoGen Definitions (see autogen.sf.net) file
# that captures the structure of the code including all
# documentation. Note that this feature is still experimental
# and incomplete at the moment.
GENERATE_AUTOGEN_DEF = NO
#---------------------------------------------------------------------------
# configuration options related to the Perl module output
#---------------------------------------------------------------------------
# If the GENERATE_PERLMOD tag is set to YES Doxygen will
# generate a Perl module file that captures the structure of
# the code including all documentation. Note that this
# feature is still experimental and incomplete at the
# moment.
GENERATE_PERLMOD = NO
# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
# the necessary Makefile rules, Perl scripts and LaTeX code to be able
# to generate PDF and DVI output from the Perl module output.
PERLMOD_LATEX = NO
# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
# nicely formatted so it can be parsed by a human reader.
# This is useful
# if you want to understand what is going on.
# On the other hand, if this
# tag is set to NO the size of the Perl module output will be much smaller
# and Perl will parse it just the same.
PERLMOD_PRETTY = YES
# The names of the make variables in the generated doxyrules.make file
# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
# This is useful so different doxyrules.make files included by the same
# Makefile don't overwrite each other's variables.
PERLMOD_MAKEVAR_PREFIX =
#---------------------------------------------------------------------------
# Configuration options related to the preprocessor
#---------------------------------------------------------------------------
# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
# evaluate all C-preprocessor directives found in the sources and include
# files.
ENABLE_PREPROCESSING = YES
# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
# names in the source code. If set to NO (the default) only conditional
# compilation will be performed. Macro expansion can be done in a controlled
# way by setting EXPAND_ONLY_PREDEF to YES.
MACRO_EXPANSION = NO
# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
# then the macro expansion is limited to the macros specified with the
# PREDEFINED and EXPAND_AS_DEFINED tags.
EXPAND_ONLY_PREDEF = NO
# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
# in the INCLUDE_PATH (see below) will be search if a #include is found.
SEARCH_INCLUDES = YES
# The INCLUDE_PATH tag can be used to specify one or more directories that
# contain include files that are not input files but should be processed by
# the preprocessor.
INCLUDE_PATH =
# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
# patterns (like *.h and *.hpp) to filter out the header-files in the
# directories. If left blank, the patterns specified with FILE_PATTERNS will
# be used.
INCLUDE_FILE_PATTERNS =
# The PREDEFINED tag can be used to specify one or more macro names that
# are defined before the preprocessor is started (similar to the -D option of
# gcc). The argument of the tag is a list of macros of the form: name
# or name=definition (no spaces). If the definition and the = are
# omitted =1 is assumed. To prevent a macro definition from being
# undefined via #undef or recursively expanded use the := operator
# instead of the = operator.
PREDEFINED = DOCPLUSLUS \
DOC_PLUS_PLUS \
P_AUDIO P_DNS P_DTMF P_EXPAT P_FTP P_HTTP P_JABBER \
P_LDAP P_ODBC P_QOS P_SNMP P_SOAP P_STUN P_URL P_VIDEO \
P_VXML P_XMLRPC P_CONFIG_FILE P_SASL2 P_HTTPFORMS \
PMEMORY_CHECK
# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
# this tag can be used to specify a list of macro names that should be expanded.
# The macro definition that is found in the sources will be used.
# Use the PREDEFINED tag if you want to use a different macro definition.
EXPAND_AS_DEFINED =
# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
# doxygen's preprocessor will remove all function-like macros that are alone
# on a line, have an all uppercase name, and do not end with a semicolon. Such
# function macros are typically used for boiler-plate code, and will confuse
# the parser if not removed.
SKIP_FUNCTION_MACROS = YES
#---------------------------------------------------------------------------
# Configuration::additions related to external references
#---------------------------------------------------------------------------
# The TAGFILES option can be used to specify one or more tagfiles.
# Optionally an initial location of the external documentation
# can be added for each tagfile. The format of a tag file without
# this location is as follows:
#
# TAGFILES = file1 file2 ...
# Adding location for the tag files is done as follows:
#
# TAGFILES = file1=loc1 "file2 = loc2" ...
# where "loc1" and "loc2" can be relative or absolute paths or
# URLs. If a location is present for each tag, the installdox tool
# does not have to be run to correct the links.
# Note that each tag file must have a unique name
# (where the name does NOT include the path)
# If a tag file is not located in the directory in which doxygen
# is run, you must also specify the path to the tagfile here.
TAGFILES =
# When a file name is specified after GENERATE_TAGFILE, doxygen will create
# a tag file that is based on the input files it reads.
GENERATE_TAGFILE =
# If the ALLEXTERNALS tag is set to YES all external classes will be listed
# in the class index. If set to NO only the inherited external classes
# will be listed.
ALLEXTERNALS = NO
# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
# in the modules index. If set to NO, only the current project's groups will
# be listed.
EXTERNAL_GROUPS = YES
# The PERL_PATH should be the absolute path and name of the perl script
# interpreter (i.e. the result of `which perl').
PERL_PATH = /usr/bin/perl
#---------------------------------------------------------------------------
# Configuration options related to the dot tool
#---------------------------------------------------------------------------
# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
# or super classes. Setting the tag to NO turns the diagrams off. Note that
# this option is superseded by the HAVE_DOT option below. This is only a
# fallback. It is recommended to install and use dot, since it yields more
# powerful graphs.
CLASS_DIAGRAMS = YES
# You can define message sequence charts within doxygen comments using the \msc
# command. Doxygen will then run the mscgen tool (see
# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
# documentation. The MSCGEN_PATH tag allows you to specify the directory where
# the mscgen tool resides. If left empty the tool is assumed to be found in the
# default search path.
MSCGEN_PATH =
# If set to YES, the inheritance and collaboration graphs will hide
# inheritance and usage relations if the target is undocumented
# or is not a class.
HIDE_UNDOC_RELATIONS = YES
# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
# available from the path. This tool is part of Graphviz, a graph visualization
# toolkit from AT&T and Lucent Bell Labs. The other options in this section
# have no effect if this option is set to NO (the default)
HAVE_DOT = NO
# By default doxygen will write a font called FreeSans.ttf to the output
# directory and reference it in all dot files that doxygen generates. This
# font does not include all possible unicode characters however, so when you need
# these (or just want a differently looking font) you can specify the font name
# using DOT_FONTNAME. You need need to make sure dot is able to find the font,
# which can be done by putting it in a standard location or by setting the
# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
# containing the font.
DOT_FONTNAME = FreeSans
# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
# The default size is 10pt.
DOT_FONTSIZE = 10
# By default doxygen will tell dot to use the output directory to look for the
# FreeSans.ttf font (which doxygen will put there itself). If you specify a
# different font using DOT_FONTNAME you can set the path where dot
# can find it using this tag.
DOT_FONTPATH =
# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
# will generate a graph for each documented class showing the direct and
# indirect inheritance relations. Setting this tag to YES will force the
# the CLASS_DIAGRAMS tag to NO.
CLASS_GRAPH = YES
# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
# will generate a graph for each documented class showing the direct and
# indirect implementation dependencies (inheritance, containment, and
# class references variables) of the class with other documented classes.
COLLABORATION_GRAPH = YES
# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
# will generate a graph for groups, showing the direct groups dependencies
GROUP_GRAPHS = YES
# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
# collaboration diagrams in a style similar to the OMG's Unified Modeling
# Language.
UML_LOOK = NO
# If set to YES, the inheritance and collaboration graphs will show the
# relations between templates and their instances.
TEMPLATE_RELATIONS = YES
# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
# tags are set to YES then doxygen will generate a graph for each documented
# file showing the direct and indirect include dependencies of the file with
# other documented files.
INCLUDE_GRAPH = YES
# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
# documented header file showing the documented files that directly or
# indirectly include this file.
INCLUDED_BY_GRAPH = YES
# If the CALL_GRAPH and HAVE_DOT options are set to YES then
# doxygen will generate a call dependency graph for every global function
# or class method. Note that enabling this option will significantly increase
# the time of a run. So in most cases it will be better to enable call graphs
# for selected functions only using the \callgraph command.
CALL_GRAPH = NO
# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
# doxygen will generate a caller dependency graph for every global function
# or class method. Note that enabling this option will significantly increase
# the time of a run. So in most cases it will be better to enable caller
# graphs for selected functions only using the \callergraph command.
CALLER_GRAPH = NO
# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
# will graphical hierarchy of all classes instead of a textual one.
GRAPHICAL_HIERARCHY = YES
# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
# then doxygen will show the dependencies a directory has on other directories
# in a graphical way. The dependency relations are determined by the #include
# relations between the files in the directories.
DIRECTORY_GRAPH = YES
# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
# generated by dot. Possible values are png, jpg, or gif
# If left blank png will be used.
DOT_IMAGE_FORMAT = png
# The tag DOT_PATH can be used to specify the path where the dot tool can be
# found. If left blank, it is assumed the dot tool can be found in the path.
DOT_PATH =
# The DOTFILE_DIRS tag can be used to specify one or more directories that
# contain dot files that are included in the documentation (see the
# \dotfile command).
DOTFILE_DIRS =
# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
# nodes that will be shown in the graph. If the number of nodes in a graph
# becomes larger than this value, doxygen will truncate the graph, which is
# visualized by representing a node as a red box. Note that doxygen if the
# number of direct children of the root node in a graph is already larger than
# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
DOT_GRAPH_MAX_NODES = 50
# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
# graphs generated by dot. A depth value of 3 means that only nodes reachable
# from the root by following a path via at most 3 edges will be shown. Nodes
# that lay further from the root node will be omitted. Note that setting this
# option to 1 or 2 may greatly reduce the computation time needed for large
# code bases. Also note that the size of a graph can be further restricted by
# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
MAX_DOT_GRAPH_DEPTH = 0
# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
# background. This is disabled by default, because dot on Windows does not
# seem to support this out of the box. Warning: Depending on the platform used,
# enabling this option may lead to badly anti-aliased labels on the edges of
# a graph (i.e. they become hard to read).
DOT_TRANSPARENT = NO
# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
# files in one run (i.e. multiple -o and -T options on the command line). This
# makes dot run faster, but since only newer versions of dot (>1.8.10)
# support this, this feature is disabled by default.
DOT_MULTI_TARGETS = NO
# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
# generate a legend page explaining the meaning of the various boxes and
# arrows in the dot generated graphs.
GENERATE_LEGEND = YES
# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
# remove the intermediate dot files that are used to generate
# the various graphs.
DOT_CLEANUP = YES
-------------- next part --------------
/*! \mainpage Portable Tools Library
\section contents Table of Contents
\li \ref intro
\li \ref overview
\li \ref using
\li \ref base
\li \ref components
\li \ref history
\section intro Introduction
This document provides reference information for the PTLib C++ class library. It is not intended
as a tutorial document.
Copyright (C) 1999-2003 Equivalence Pty Ltd, All right reserved<BR>
Portions Copyright (C) 2004 Post Increment, All Rights Reserved<BR>
Portions Copyright (C) 2009 Vox Lucida Pty, Ltd., All Rights Reserved
\section overview Overview
PTLib is a moderately large C++ class library that originated many years ago as
a method to produce applications that run on both Microsoft Windows and Unix
X-Windows systems. It also was to have a Macintosh port as well, but this never
eventuated. In those days it was called the PWLib the Portable Windows Library.
Since then, the availability of multi-platform GUI toolkits such as KDE and wxWindows,
and the development of the OpenH323 and OPAL projects as primary user of the library,
has emphasised the focus on networking, I/O portability, multi-threading
and protocol portability. Mostly, the library is used to create high performance and
highly portable network-centric applications. So all the GUI abstractions ahave been
dropped and it was renamed the Portable Tools Library that you see today.
In addition to these high level functions, basic "container" classes such as arrays,
linear lists, sorted lists (RB Tree) and dictionaries (hash tables) are available. These
were created before the emergence of STL as a standard, so unfortunately these
constructs are incompatible with iterators and generic algorithms.
Development continues in this area, and future versions of PTLib will see increased
use of, and compatibility with, STL, but it is a long and slow process.
The library is used extensively by many companies for both commercial and Open Source
products. The motivation in making PTLib available as Open Source was primarily to
support the OpenH323 and OPAL projects, but it is definitely useful as a stand-alone
library to anyone that wishes to write portable applications.
The classes within PTLib are seperated into two types:
\ref base
and
\ref components
The
\ref base
contain all of the essential support for constructs such as containers, threads and sockets
that are dependent on platform specific features. All PTLib programs will require the
\ref base
The
\ref components
implement functionality that is usually platform independent, and may not be required
for all programs. On some platforms (notably Windows) the
\ref base
and
\ref components
may be divided
into discrete library archives. Other platforms (notably Unix platforms) combine all of the code into a single library
and rely on the linker to omit code that is not required.
Note that previous versions of PTLib also contained GUI classes and GUI components, but support for these
classes has been discontinued.
\section using Using PTLib
Tutorial introductions for PTLib are available elsewhere (see http://toncar.cz/openh323/tut), but some
information on how to create a simple program is always useful.
Here is the canonical "Hello world!" program written using the PTLib infrastructure.
\verbatim
// hello.cxx
#include <ptlib.h>
class Hello : public PProcess
{
PCLASSINFO(Hello, PProcess)
public:
void Main();
};
PCREATE_PROCESS(Hello)
void Hello::Main()
{
cout << "Hello world!\n";
}
// End of hello.cxx
\endverbatim
The PCREATE_PROCESS macro actually defines the main() function
and creates an instance of Hello. This assures that everything is
initialised in the correct order. C++ does initialisation of global
statics badly (and destruction is even worse), so try to put
everything into your PProcess descedent rather than globals.
\section base Base Classes
\subsection object_h Base Object and Container Classes
\li PObject - the base class for all other classes in the PTLib.
\li PContainer - the base class for all reference-counted classes in PTLib.
\li PArray - base class for array of objects. Equivalent to the STL vector template class.
\li PList - base class for lists of objects. Equivalent to the STL list template class.
\li PDictionary - base class for dictionaries. Equivalent to the STL map template class.
\li PSet - base class for sets. Equivalent to the STL set template class.
\li PString - base class for the string abstraction. Equivalent to the STL string class.
\li PCaselessString - class for a string that ignores case.
\li PSmartPointer - a reference counted pointer
\li PSmartNotifierFunction - a smart notifier function that uses object IDs rather than pointers
\li PNotifier - a notifier function that allows any class to call a member function on any other class
\subsection channel I/O Channel Classes
Classes that perform general I/O using the PChannel abstraction
\li PChannel - base class for all I/O channels
\li PIndirectChannel - a channel that encapsulates another channel
\li PConsoleChannel - channel for accessing the system console
\li PPipeChannel - execute a program and access input and output as a PChannel
\li PQueueChannel - pure memory version of a pipe PChannel
\li PSerialChannel - access a serial communications port as a PChannel
\li PModem - a descendant of PSerialChannel that is customised for modems that obey the AT command set
\li PFile - access files on the host operating system using PChannels
\li PTextFile - access text files on the host operating system as PChannel
\li PStructuredFile - access files on the host operating system as arrays of structured records
\li PMemoryFile - implements a PFile descendant that stores data in memory
\li PFilePath - access directories on the host operating system
\li PSoundChannel - read or write data to sound device as a PChannel
\subsection socket Socket Classes
Implementation of a network sockets abstraction (roughly based on Berkeley sockets)
\li PSocket - base class for all network sockets
\li PIPSocket - base class for all sockets using the IP protocol
\li PIPSocket::Address - representation of an IP address
\li PUDPSocket - IP socket using the UDP protocol
\li PTCPSocket - IP socket using the TCP/IP protocol
\li PICMPSocket - IP socket using the ICMP protocl
\li PEthSocket - socket interface for raw Ethernet interfaces
\subsection thread Process and Thread Classes
Classes that handle processes, multi-threading and synchronsiation.
\li PProcess - implements the primary thread of control for a running program
\li PServiceProcess - implements a "daemon" or "system process"
\li PDynaLink - abstraction for dynamic or sharabel libraries, loadable at run-time.
\li PThread - abstracts a thread of control or execution context
\li PThreadPool - manage a pool of threads for execution.
\li PSemaphore - synchronisation primitive based on a counter
\li PMutex - synchronisation primitive based on mutual exclusion
\li PSyncPoint - allows multiple threads to sychronise to a specific code point. See also PSyncPointAck
\li PReadWriteMutex - mutex that allows multiple readers, single writer model.
\li PAtomicInteger - implements an integer counter with atomic increment and decrement operations
\li PSafeObject - base class for objects used by the PSafeCollection system.
\subsection thread Operating System Classes
Classes that normalise other opeating system functions.
\li PConfig - provide persistent storage for program settings using a platform-appropriate mechanism
\li PTime - abstracts the notion of a wall-clock time and date
\li PTimeInterval - abstracts the notion of a time interval as the difference between two PTime values
\li PTimer - one shot or continuous timers with optional execution of a function on expiry.
\li PMail - send an email using a platform-appropriate mechanism
\li PTextToSpeech - Implement a Text to Speech converter
\li PRemoteConnection - controls for a dialup network connection
\li PVideoDevice - abstract class for video devices
\section components Console Components
\subsection protocol Protocol Classes
Implementation of various Internet-related protocols. Some of these are implemented within PTLib - some require external libraries for support
\li PInternetProtocol - base class for all text-based Internet protocols
\li PPOP3 - base class for POP3 protocol classes. See also PPOP3Client and PPOP3Server
\li PSMTP - base class for SMTP protocol classes. See also PSMTPClient and PSMTPServer
\li PFTP - base class for FTP protocol classes. See also PFTPClient and FTPServer
\li PMIMEInfo - implements a list of key-value pairs in MIME format
\li PTelnetSocket - implements the TELNET protocol
\li PSocksProtocol - base class for SOCKS protocol implementation. See also PSocks4Socket, PSocks5Socket, PSocksSocket, PSocksUDPSocket
\li PSTUNClient - implementation of a STUN client
\li PSNMP - base classs for SNMP protocol implementations. See also PSNMPClient and PSNMPServer
\li PSSLChannel - PIndirectChannel that implements the SSL protocol via OpenSSL.
\li PSASLClient - implements the SASL protocol via the Cyrus SASL library
\li PXMLRPC - implements the XMLRPC protocol via the Expat XML library and the HTTP classes
\li PSOAPClient - implements a SOAP client
\li PLDAPSession - implements a LDAP client via the OpenLDAP library
\li PILSSession - implements a ILS client via the OpenLDAP library
\li XMPP::Stream - implements a XMPP (Jabber) stream as a PChannel.
\subsection http HTTP Classes
Implementation of the HTTP protocol
\li PHTTP - base class for HTTP protocol. See also PHTTPClient and PHTTPServer
\li PURL - parse and maniulate uniform resource locations
\li PHTML - a string stream that formats HTML information
\li PHTTPForm - allows the creation of HTTP forms
\li PHTTPServiceProcess - a PServiceProcess descendant that contains a HTTP server
\subsection misccomponents Miscellaneous Classes
\li PPluginManager - manage plugin code modules
\li PArgList - parse a command line passed to a console program
\li PRandom - a random number generator
\li PAdaptiveDelay - class to make delays as constant as possible despite operating system errors.
\li PFactory - an implementation of the "Factory" paradigm using templates
\li PRegularExpression - class for handling regular expression parsing.
\li PIpAccessControlList - a list of entries that allow specification of a range of IP addresses or networks
\li PCypher - implementation of various code cyphers such as PMessageDigest5, PTEACypher, and PMessageDigestSHA1
\li PBase64 - Base 64 encoder/decoder.
\li PWAVFile - implements a AIFF format WAV file
\li PDTMFDecoder - decodes DTMF digits from a stream of PCM data
\li PXML - Implements a parser for XML using the Expat library
\li PVXMLChannel - Implements a parser for the VXML language
\li PCLI - command line interpreter.
\subsection history History
\li 17 May 2004 - Converted from Doc++ to Doxygen format by Craig Southeren
5 Apr 2010 - Major clean up of documentation inconsistencies.
*/
-------------- next part --------------
/*
* object.h
*
* Mother of all ancestor classes.
*
* Portable Tools Library
*
* Copyright (c) 1993-1998 Equivalence Pty. Ltd.
*
* The contents of this file are subject to the Mozilla Public License
* Version 1.0 (the "License"); you may not use this file except in
* compliance with the License. You may obtain a copy of the License at
* http://www.mozilla.org/MPL/
*
* Software distributed under the License is distributed on an "AS IS"
* basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
* the License for the specific language governing rights and limitations
* under the License.
*
* The Original Code is Portable Windows Library.
*
* The Initial Developer of the Original Code is Equivalence Pty. Ltd.
*
* Portions are Copyright (C) 1993 Free Software Foundation, Inc.
* All Rights Reserved.
*
* Contributor(s): ______________________________________.
*
* $Revision: 28201 $
* $Author: rjongbloed $
* $Date: 2012-08-14 21:30:31 -0500 (Tue, 14 Aug 2012) $
*/
#ifndef PTLIB_OBJECT_H
#define PTLIB_OBJECT_H
#ifdef P_USE_PRAGMA
#pragma interface
#endif
#if defined(_WIN32) || defined(_WIN32_WCE)
#include "msos/ptlib/contain.h"
#else
#include "unix/ptlib/contain.h"
#endif
#if defined(P_VXWORKS)
#include <private/stdiop.h>
#endif
#include <stdio.h>
#include <stdarg.h>
#include <stdlib.h>
#include <string.h>
#include <string>
#include <iomanip>
#include <iostream>
#include <sstream>
#include <vector>
#include <list>
#include <map>
#include <algorithm>
#define P_REMOVE_VIRTUAL_INTERNAL_BASE(fn) __inline virtual struct ptlib_virtual_function_changed_or_removed ****** fn { return 0; }
#if defined(_MSC_VER)
#if _MSC_VER < 1310
#define P_DEPRECATED
#define P_REMOVE_VIRTUAL_INTERNAL(type, fn, body) P_REMOVE_VIRTUAL_INTERNAL_BASE(fn)
#elif _MSC_VER < 1400
#define P_DEPRECATED __declspec(deprecated)
#define P_REMOVE_VIRTUAL_INTERNAL(type, fn, body) __inline virtual __declspec(deprecated) type fn body
#else
#define P_DEPRECATED __declspec(deprecated)
#define P_REMOVE_VIRTUAL_INTERNAL(type, fn, body) __inline virtual __declspec(deprecated("Virtual function signature changed or function deprecated")) type fn body
#endif
#elif defined(__GNUC__)
#if __GNUC__ < 4
#define P_DEPRECATED
#define P_REMOVE_VIRTUAL_INTERNAL(type, fn, body) P_REMOVE_VIRTUAL_INTERNAL_BASE(fn)
#else
#define P_DEPRECATED __attribute__((deprecated))
#define P_REMOVE_VIRTUAL_INTERNAL(type, fn, body) __attribute__((warn_unused_result)) __attribute__((deprecated)) P_REMOVE_VIRTUAL_INTERNAL_BASE(fn)
#endif
#else
#define P_DEPRECATED
#define P_REMOVE_VIRTUAL_INTERNAL(type, fn, body) P_REMOVE_VIRTUAL_INTERNAL_BASE(fn)
#endif
#define P_REMOVE_VIRTUAL_VOID(fn) P_REMOVE_VIRTUAL_INTERNAL(void, fn, {})
#define P_REMOVE_VIRTUAL(type, fn, ret) P_REMOVE_VIRTUAL_INTERNAL(type, fn, { return ret; })
// P_USE_INTEGER_BOOL is the default and gives the old behaviour (it
// is also used for C translation units).
// without P_USE_INTEGER_BOOL, the ANSI C++ bool is used.
#if defined(P_USE_INTEGER_BOOL) || !defined(__cplusplus)
typedef BOOL PBoolean;
# define PTrue TRUE
# define PFalse FALSE
#else
typedef bool PBoolean;
# define PTrue true
# define PFalse false
#endif
///////////////////////////////////////////////////////////////////////////////
// Disable inlines when debugging for faster compiles (the compiler doesn't
// actually inline the function with debug on any way).
#ifndef P_USE_INLINES
#ifdef _DEBUG
#define P_USE_INLINES 0
#else
#define P_USE_INLINES 0
#endif
#endif
#if P_USE_INLINES
#define PINLINE inline
#else
#define PINLINE
#endif
///////////////////////////////////////////////////////////////////////////////
// Declare the debugging support
#ifndef P_USE_ASSERTS
#define P_USE_ASSERTS 1
#endif
#if !P_USE_ASSERTS
#define PAssert(b, m) (b)
#define PAssert2(b, c, m) (b)
#define PAssertOS(b) (b)
#define PAssertNULL(p) (p)
#define PAssertAlways(m) {}
#define PAssertAlways2(c, m) {}
#else // P_USE_ASSERTS
/// Standard assert messages for the PAssert macro.
enum PStandardAssertMessage {
PLogicError, ///< A logic error occurred.
POutOfMemory, ///< A new or malloc failed.
PNullPointerReference, ///< A reference was made through a NULL pointer.
PInvalidCast, ///< An invalid cast to descendant is required.
PInvalidArrayIndex, ///< An index into an array was negative.
PInvalidArrayElement, ///< A NULL array element object was accessed.
PStackEmpty, ///< A Pop() was made of a stack with no elements.
PUnimplementedFunction, ///< Funtion is not implemented.
PInvalidParameter, ///< Invalid parameter was passed to a function.
POperatingSystemError, ///< Error was returned by Operating System.
PChannelNotOpen, ///< Operation attempted when channel not open.
PUnsupportedFeature, ///< Feature is not supported.
PInvalidWindow, ///< Access through invalid window.
PMaxStandardAssertMessage ///< Number of standard assert message.
};
#define __CLASS__ NULL
void PAssertFunc(const char * file, int line, const char * className, PStandardAssertMessage msg);
void PAssertFunc(const char * file, int line, const char * className, const char * msg);
void PAssertFunc(const char * full_msg);
inline bool PAssertFuncInline(bool b, const char * file, int line, const char * className, PStandardAssertMessage msg)
{
if (!b)
PAssertFunc(file, line, className, msg);
return b;
}
inline bool PAssertFuncInline(bool b, const char * file, int line, const char * className, const char * msg)
{
if (!b)
PAssertFunc(file, line, className, msg);
return b;
}
/** This macro is used to assert that a condition must be true.
If the condition is false then an assert function is called with the source
file and line number the macro was instantiated on, plus the message described
by the <code>msg</code> parameter. This parameter may be either a standard value
from the <code>PStandardAssertMessage</code> enum or a literal string.
*/
#define PAssert(b, msg) PAssertFuncInline((b), __FILE__,__LINE__,__CLASS__,(msg))
/** This macro is used to assert that a condition must be true.
If the condition is false then an assert function is called with the source
file and line number the macro was instantiated on, plus the message described
by the <code>msg</code> parameter. This parameter may be either a standard value
from the <code>PStandardAssertMessage</code> enum or a literal string.
The <code>cls</code> parameter specifies the class name that the error occurred in
*/
#define PAssert2(b, cls, msg) PAssertFuncInline((b), __FILE__,__LINE__,(cls),(msg))
/** This macro is used to assert that an operating system call succeeds.
If the condition is false then an assert function is called with the source
file and line number the macro was instantiated on, plus the message
described by the <code>POperatingSystemError</code> value in the <code>PStandardAssertMessage</code>
enum.
*/
#define PAssertOS(b) PAssertFuncInline((b), __FILE__,__LINE__,__CLASS__,POperatingSystemError)
/** This macro is used to assert that a pointer must be non-null.
If the pointer is NULL then an assert function is called with the source file
and line number the macro was instantiated on, plus the message described by
the PNullPointerReference value in the <code>PStandardAssertMessage</code> enum.
Note that this evaluates the expression defined by <code>ptr</code> twice. To
prevent incorrect behaviour with this, the macro will assume that the
<code>ptr</code> parameter is an L-Value.
*/
#define PAssertNULL(ptr) (((ptr)!=NULL)?(ptr): \
(PAssertFunc(__FILE__,__LINE__, __CLASS__, PNullPointerReference),(ptr)))
/** This macro is used to assert immediately.
The assert function is called with the source file and line number the macro
was instantiated on, plus the message described by the <code>msg</code> parameter. This
parameter may be either a standard value from the <code>PStandardAssertMessage</code>
enum or a literal string.
*/
#define PAssertAlways(msg) PAssertFunc(__FILE__,__LINE__,__CLASS__,(msg))
/** This macro is used to assert immediately.
The assert function is called with the source file and line number the macro
was instantiated on, plus the message described by the <code>msg</code> parameter. This
parameter may be either a standard value from the <code>PStandardAssertMessage</code>
enum or a literal string.
*/
#define PAssertAlways2(cls, msg) PAssertFunc(__FILE__,__LINE__,(cls),(msg))
#endif // P_USE_ASSERTS
/** Get the stream being used for error output.
This stream is used for all trace output using the various trace functions
and macros.
*/
ostream & PGetErrorStream();
/** Set the stream to be used for error output.
This stream is used for all error output using the <code>PError</code> macro.
*/
void PSetErrorStream(ostream * strm /** New stream for error output */ );
/** This macro is used to access the platform specific error output stream.
This is to be used in preference to assuming <code>cerr</code> is always available. On
Unix platforms this {\b is} <code>cerr</code> but for MS-Windows this is another stream
that uses the OutputDebugString() Windows API function. Note that a MS-DOS or
Windows NT console application would still use <code>cerr</code>.
The <code>PError</code> stream would normally only be used for debugging information as
a suitable display is not always available in windowed environments.
The macro is a wrapper for a global variable error stream. The internal variable
is initialised to <i>std::cerr</i> for all but MS-Windows and NT GUI applications.
An application could change this pointer to a <i>std::ofstream</i> variable of
#PError output is wished to be redirected to a file.
*/
#define PError (PGetErrorStream())
///////////////////////////////////////////////////////////////////////////////
// Debug and tracing
#ifndef PTRACING
#define PTRACING 1
#endif
#if PTRACING
/**Class to encapsulate tracing functions.
This class does not require any instances and is only being used as a
method of grouping functions together in a name space.
There are a number of macros for supporting tracing. These will all
evaluate as empty in a "No Trace" build of the system:
- PTRACE()
- PTRACE_IF()
- PTRACE_PARAM()
- PTRACE_BLOCK()
- PTRACE_LINE()
*/
class PTrace
{
public:
/// Options for trace output.
enum Options {
/**Include PTrace::Block constructs in output
If this is bit is clear, all PTrace::Block output is inhibited
regardless of the trace level. If set, the PTrace::Block may occur
provided the trace level is greater than zero.
*/
Blocks = 1,
/// Include date and time in all output
DateAndTime = 2,
/// Include (millisecond) timestamp in all output
Timestamp = 4,
/// Include identifier for thread trace is made from in all output
Thread = 8,
/// Include trace level in all output
TraceLevel = 16,
/// Include the file and line for the trace call in all output
FileAndLine = 32,
/// Include thread object pointer address in all trace output
ThreadAddress = 64,
/// Append to log file rather than resetting every time
AppendToFile = 128,
/// Output timestamps in GMT time rather than local time
GMTTime = 256,
/// If set, log file will be rotated daily
RotateDaily = 512,
/// If set, log file will be rotated hourly
RotateHourly = 1024,
/// If set, log file will be rotated every minute
RotateMinutely = 2048,
/// Mask for all the rotate bits
RotateLogMask = RotateDaily + RotateHourly + RotateMinutely,
/** SystemLog flag for tracing within a PServiceProcess application. Must
be set in conjection with <code>#SetStream(new PSystemLog)</code>.
*/
SystemLogStream = 32768
};
/**Set the most common trace options.
If \p filename is not NULL then a PTextFile is created and attached the
trace output stream. This object is never closed or deleted until the
termination of the program.
There are several special values for \p filename:
<dl>
<dt>"stderr" <dd>Output to standard error
<dt>"stdout" <dd>Output to standard output
<dt>"DEBUGSTREAM" <dd>Output to debugger (Windows only)
</dl>
A trace output of the program name version and OS is written as well.
*/
static void Initialise(
unsigned level, ///< Level for tracing
const char * filename = NULL, ///< Filename for log output
unsigned options = Timestamp | Thread | Blocks ///< #Options for tracing
);
/**Set the most common trace options.
If \p filename is not NULL then a PTextFile is created and attached the
trace output stream. This object is never closed or deleted until the
termination of the program.
If \p rolloverPatterm is not NULL it is used as the time format patterm
appended to filename if the #RotateDaily is set. Default is "yyyy_MM_dd".
A trace output of the program name version and OS is written as well.
*/
static void Initialise(
unsigned level, ///< Level for tracing
const char * filename, ///< Filename for log output
const char * rolloverPattern, ///< Pattern for rolling over trace files
unsigned options = Timestamp | Thread | Blocks ///< #Options for tracing
);
/** Set the trace options.
The PTRACE(), PTRACE_BLOCK() and PTRACE_LINE() macros output trace text that
may contain assorted values. These are defined by the #Options enum.
Note this function OR's the bits included in the options parameter.
*/
static void SetOptions(
unsigned options ///< New option bits for tracing
);
/** Clear the trace options.
The <code>PTRACE()</code>, <code>PTRACE_BLOCK()</code> and
<code>PTRACE_LINE()</code> macros output trace text that
may contain assorted values. These are defined by the #Options enum.
Note this function AND's the complement of the bits included in the options
parameter.
*/
static void ClearOptions(
unsigned options ///< Option bits to turn off
);
/** Get the current trace options.
The <code>PTRACE()</code>, <code>PTRACE_BLOCK()</code> and
<code>PTRACE_LINE()</code> macros output trace text that
may contain assorted values. These are defined by the #Options enum.
*/
static unsigned GetOptions();
/** Set the trace level.
The <code>PTRACE()</code> macro checks to see if its level is equal to or lower then the
level set by this function. If so then the trace text is output to the trace
stream.
*/
static void SetLevel(
unsigned level ///< New level for tracing
);
/** Get the trace level.
The <code>PTRACE()</code> macro checks to see if its level is equal to or lower then the
level set by this function. If so then the trace text is output to the trace
stream.
*/
static unsigned GetLevel();
/** Determine if the level may cause trace output.
This checks against the current global trace level set by SetLevel()
for if the trace output may be emitted. This is used by the PTRACE() macro.
*/
static PBoolean CanTrace(
unsigned level ///< Trace level to check
);
/** Set the stream to be used for trace output.
This stream is used for all trace output using the various trace functions
and macros.
*/
static void SetStream(
ostream * out ///< New output stream from trace.
);
/** Begin a trace output.
If the trace stream output is used outside of the provided macros, it
should be noted that a mutex is obtained on the call to Begin() which
will prevent any other threads from using the trace stream until the
End() function is called.
So a typical usage would be:
<pre><code>
ostream & s = PTrace::Begin(3, __FILE__, __LINE__);
s << "hello";
if (want_there)
s << " there";
s << '!' << PTrace::End;
</code></pre>
*/
static ostream & Begin(
unsigned level, ///< Log level for output
const char * fileName, ///< Filename of source file being traced
int lineNum ///< Line number of source file being traced.
);
/** End a trace output.
If the trace stream output is used outside of the provided macros, the
End() function must be used at the end of the section of trace
output. A mutex is obtained on the call to Begin() which will prevent
any other threads from using the trace stream until the End(). The
End() is used in a similar manner to <code>std::endl</code> or
<code>std::flush</code>.
So a typical usage would be:
<pre><code>
ostream & s = PTrace::Begin();
s << "hello";
if (want_there)
s << " there";
s << '!' << PTrace::End;
</code></pre>
*/
static ostream & End(
ostream & strm ///< Trace output stream being completed
);
/** Cleanup the trace system for a specific thread
When using thread local storage, this will delete the per-thread trace context
*/
static void Cleanup();
/** Class to trace Execution blocks.
This class is used for tracing the entry and exit of program blocks. Upon
construction it outputs an entry trace message and on destruction outputs an
exit trace message. This is normally only used from in the <code>PTRACE_BLOCK()</code> macro.
*/
class Block {
public:
/** Output entry trace message. */
Block(
const char * fileName, ///< Filename of source file being traced
int lineNum, ///< Line number of source file being traced.
const char * traceName
///< String to be output with trace, typically it is the function name.
);
Block(const Block & obj)
: file(obj.file), line(obj.line), name(obj.name) { }
/// Output exit trace message.
~Block();
private:
Block & operator=(const Block &)
{ return *this; }
const char * file;
int line;
const char * name;
};
};
/* Macro to conditionally declare a parameter to a function to avoid compiler
warning due that parameter only being used in a <code>PTRACE()</code> */
#define PTRACE_PARAM(param) param
/** Trace an execution block.
This macro creates a trace variable for tracking the entry and exit of program
blocks. It creates an instance of the PTraceBlock class that will output a
trace message at the line <code>PTRACE_BLOCK()</code> is called and then on exit from the
scope it is defined in.
*/
#define PTRACE_BLOCK(name) PTrace::Block __trace_block_instance(__FILE__, __LINE__, name)
/** Trace the execution of a line.
This macro outputs a trace of a source file line execution.
*/
#define PTRACE_LINE() \
if (PTrace::CanTrace(1)) \
PTrace::Begin(1, __FILE__, __LINE__) << __FILE__ << '(' << __LINE__ << ')' << PTrace::End; \
else (void)0
/** Output trace.
This macro outputs a trace of any information needed, using standard stream
output operators. The output is only made if the trace level set by the
SetLevel() function is greater than or equal to the \p level argument.
*/
#define PTRACE(level, args) \
if (PTrace::CanTrace(level)) \
PTrace::Begin(level, __FILE__, __LINE__) << args << PTrace::End; \
else (void)0
/** Output trace on condition.
This macro outputs a trace of any information needed, using standard stream
output operators. The output is only made if the trace level set by the
SetLevel() function is greater than or equal to the <code>level</code> argument
and the conditional is true. Note the conditional is only evaluated if the
trace level is sufficient.
*/
#define PTRACE_IF(level, cond, args) \
if ((PTrace::CanTrace(level) && (cond))) \
PTrace::Begin(level, __FILE__, __LINE__) << args << PTrace::End; \
else (void)0
#else // PTRACING
#define PTRACE_PARAM(param)
#define PTRACE_BLOCK(n)
#define PTRACE_LINE()
#define PTRACE(level, arg)
#define PTRACE_IF(level, cond, args)
#endif // PTRACING
#if PMEMORY_CHECK || (defined(_MSC_VER) && defined(_DEBUG) && !defined(_WIN32_WCE))
#define PMEMORY_HEAP 1
/** Memory heap checking class.
This class implements the memory heap checking and validation functions. It
maintains lists of allocated block so that memory leaks can be detected. It
also initialises memory on allocation and deallocation to help catch errors
involving the use of dangling pointers.
*/
class PMemoryHeap {
public:
/// Initialise the memory checking subsystem.
PMemoryHeap();
// Clear up the memory checking subsystem, dumping memory leaks.
~PMemoryHeap();
/** Allocate a memory block.
This allocates a new memory block and keeps track of it. The memory
block is filled with the value in the <code>allocFillChar</code> member variable
to help detect uninitialised structures.
@return pointer to newly allocated memory block.
*/
static void * Allocate(
size_t nSize, ///< Number of bytes to allocate.
const char * file, ///< Source file name for allocating function.
int line, ///< Source file line for allocating function.
const char * className ///< Class name for allocating function.
);
/** Allocate a memory block.
This allocates a new memory block and keeps track of it. The memory
block is filled with the value in the <code>allocFillChar</code> member variable
to help detect uninitialised structures.
@return pointer to newly allocated memory block.
*/
static void * Allocate(
size_t count, ///< Number of items to allocate.
size_t iSize, ///< Size in bytes of each item.
const char * file, ///< Source file name for allocating function.
int line ///< Source file line for allocating function.
);
/** Change the size of an allocated memory block.
This allocates a new memory block and keeps track of it. The memory
block is filled with the value in the <code>allocFillChar</code> member variable
to help detect uninitialised structures.
@return pointer to reallocated memory block. Note this may
{\em not} be the same as the pointer passed into the function.
*/
static void * Reallocate(
void * ptr, ///< Pointer to memory block to reallocate.
size_t nSize, ///< New number of bytes to allocate.
const char * file, ///< Source file name for allocating function.
int line ///< Source file line for allocating function.
);
/** Free a memory block.
The memory is deallocated, a warning is displayed if it was never
allocated. The block of memory is filled with the value in the
<code>freeFillChar</code> member variable.
*/
static void Deallocate(
void * ptr, ///< Pointer to memory block to deallocate.
const char * className ///< Class name for deallocating function.
);
/** Validation result.
*/
enum Validation {
Ok, Bad, Trashed
};
/** Validate the memory pointer.
The <code>ptr</code> parameter is validated as a currently allocated heap
variable.
@return Ok for pointer is in heap, Bad for pointer is not in the heap
or Trashed if the pointer is in the heap but has overwritten the guard
bytes before or after the actual data part of the memory block.
*/
static Validation Validate(
const void * ptr, ///< Pointer to memory block to check
const char * className, ///< Class name it should be.
ostream * error ///< Stream to receive error message (may be NULL)
);
/** Validate all objects in memory.
This effectively calls Validate() on every object in the heap.
@return true if every object in heap is Ok.
*/
static PBoolean ValidateHeap(
ostream * error = NULL ///< Stream to output, use default if NULL
);
/** Ignore/Monitor allocations.
Set internal flag so that allocations are not included in the memory
leak check on program termination.
Returns the previous state.
*/
static PBoolean SetIgnoreAllocations(
PBoolean ignore ///< New flag for allocation ignoring.
);
/** Get memory check system statistics.
Dump statistics output to the default stream.
*/
static void DumpStatistics();
/** Get memory check system statistics.
Dump statistics output to the specified stream.
*/
static void DumpStatistics(ostream & strm /** Stream to output to */);
#if PMEMORY_CHECK
struct State {
DWORD allocationNumber;
};
#else
typedef _CrtMemState State;
#endif
/* Get memory state.
This returns a state that may be used to determine where to start dumping
objects from.
*/
static void GetState(
State & state ///< Memory state
);
/** Dump allocated objects.
Dump ojects allocated and not deallocated since the specified object
number. This would be a value returned by the <code>GetAllocationRequest()</code>
function.
Output is to the default stream.
*/
static void DumpObjectsSince(
const State & when ///< Memory state to begin dump from.
);
/** Dump allocated objects.
Dump ojects allocated and not deallocated since the specified object
number. This would be a value returned by the <code>GetAllocationRequest()</code>
function.
*/
static void DumpObjectsSince(
const State & when, ///< Memory state to begin dump from.
ostream & strm ///< Stream to output dump
);
/** Set break point allocation number.
Set the allocation request number to cause an assert. This allows a
developer to cause a halt in a debugger on a certain allocation allowing
them to determine memory leaks allocation point.
*/
static void SetAllocationBreakpoint(
DWORD point ///< Allocation number to stop at.
);
#if PMEMORY_CHECK
protected:
void * InternalAllocate(
size_t nSize, // Number of bytes to allocate.
const char * file, // Source file name for allocating function.
int line, // Source file line for allocating function.
const char * className // Class name for allocating function.
);
Validation InternalValidate(
const void * ptr, // Pointer to memory block to check
const char * className, // Class name it should be.
ostream * error // Stream to receive error message (may be NULL)
);
void InternalDumpStatistics(ostream & strm);
void InternalDumpObjectsSince(DWORD objectNumber, ostream & strm);
class Wrapper {
public:
Wrapper();
~Wrapper();
PMemoryHeap * operator->() const { return instance; }
private:
PMemoryHeap * instance;
};
friend class Wrapper;
enum Flags {
NoLeakPrint = 1
};
#pragma pack(1)
struct Header {
enum {
// Assure that the Header struct is aligned to 8 byte boundary
NumGuardBytes = 16 - (sizeof(Header *) +
sizeof(Header *) +
sizeof(const char *) +
sizeof(const char *) +
sizeof(size_t) +
sizeof(DWORD) +
sizeof(WORD) +
sizeof(BYTE)
#if P_PTHREADS
+ sizeof(pthread_t)
#endif
)%8
};
Header * prev;
Header * next;
const char * className;
const char * fileName;
size_t size;
DWORD request;
WORD line;
BYTE flags;
#if P_PTHREADS
pthread_t thread;
#endif
char guard[NumGuardBytes];
static char GuardBytes[NumGuardBytes];
};
#pragma pack()
PBoolean isDestroyed;
Header * listHead;
Header * listTail;
static DWORD allocationBreakpoint;
DWORD allocationRequest;
DWORD firstRealObject;
BYTE flags;
char allocFillChar;
char freeFillChar;
DWORD currentMemoryUsage;
DWORD peakMemoryUsage;
DWORD currentObjects;
DWORD peakObjects;
DWORD totalObjects;
ostream * leakDumpStream;
#if defined(_WIN32)
CRITICAL_SECTION mutex;
#elif defined(P_PTHREADS)
pthread_mutex_t mutex;
#elif defined(P_VXWORKS)
void * mutex;
#endif
#else
#define P_CLIENT_BLOCK (_CLIENT_BLOCK|(0x61<<16)) // This identifies a PObject derived class
_CrtMemState initialState;
#endif // PMEMORY_CHECK
};
/** Allocate memory for the run time library.
This version of free is used for data that is not to be allocated using the
memory check system, ie will be free'ed inside the C run time library.
*/
inline void * runtime_malloc(size_t bytes /** Size of block to allocate */ ) { return malloc(bytes); }
/** Free memory allocated by run time library.
This version of free is used for data that is not allocated using the
memory check system, ie was malloc'ed inside the C run time library.
*/
inline void runtime_free(void * ptr /** Memory block to free */ ) { free(ptr); }
/** Override of system call for memory check system.
This macro is used to allocate memory via the memory check system selected
with the <code>PMEMORY_CHECK</code> compile time option. It will include the source file
and line into the memory allocation to allow the PMemoryHeap class to keep
track of the memory block.
*/
#define malloc(s) PMemoryHeap::Allocate(s, __FILE__, __LINE__, NULL)
/** Override of system call for memory check system.
This macro is used to allocate memory via the memory check system selected
with the <code>PMEMORY_CHECK</code> compile time option. It will include the source file
and line into the memory allocation to allow the PMemoryHeap class to keep
track of the memory block.
*/
#define calloc(n,s) PMemoryHeap::Allocate(n, s, __FILE__, __LINE__)
/** Override of system call for memory check system.
This macro is used to allocate memory via the memory check system selected
with the <code>PMEMORY_CHECK</code> compile time option. It will include the source file
and line into the memory allocation to allow the PMemoryHeap class to keep
track of the memory block.
*/
#define realloc(p,s) PMemoryHeap::Reallocate(p, s, __FILE__, __LINE__)
/** Override of system call for memory check system.
This macro is used to deallocate memory via the memory check system selected
with the <code>PMEMORY_CHECK</code> compile time option. It will include the source file
and line into the memory allocation to allow the PMemoryHeap class to keep
track of the memory block.
*/
#define free(p) PMemoryHeap::Deallocate(p, NULL)
/** Override of system call for memory check system.
This macro is used to deallocate memory via the memory check system selected
with the <code>PMEMORY_CHECK</code> compile time option. It will include the source file
and line into the memory allocation to allow the PMemoryHeap class to keep
track of the memory block.
*/
#define cfree(p) PMemoryHeap::Deallocate(p, NULL)
/** Macro for overriding system default <code>new</code> operator.
This macro is used to allocate memory via the memory check system selected
with the PMEMORY_CHECK compile time option. It will include the source file
and line into the memory allocation to allow the PMemoryHeap class to keep
track of the memory block.
This macro could be used instead of the system <code>new</code> operator. Or you can place
the line
<pre><code>
#define new PNEW
</code></pre>
at the begining of the source file, after all declarations that use the
<code>#PCLASSINFO</code> macro.
*/
#define PNEW new (__FILE__, __LINE__)
#if !defined(_MSC_VER) || _MSC_VER<1200
#define PSPECIAL_DELETE_FUNCTION
#else
#define PSPECIAL_DELETE_FUNCTION \
void operator delete(void * ptr, const char *, int) \
{ PMemoryHeap::Deallocate(ptr, Class()); } \
void operator delete[](void * ptr, const char *, int) \
{ PMemoryHeap::Deallocate(ptr, Class()); }
#endif
#define PNEW_AND_DELETE_FUNCTIONS \
void * operator new(size_t nSize, const char * file, int line) \
{ return PMemoryHeap::Allocate(nSize, file, line, Class()); } \
void * operator new(size_t nSize) \
{ return PMemoryHeap::Allocate(nSize, NULL, 0, Class()); } \
void operator delete(void * ptr) \
{ PMemoryHeap::Deallocate(ptr, Class()); } \
void * operator new(size_t, void * placement) \
{ return placement; } \
void operator delete(void *, void *) \
{ } \
void * operator new[](size_t nSize, const char * file, int line) \
{ return PMemoryHeap::Allocate(nSize, file, line, Class()); } \
void * operator new[](size_t nSize) \
{ return PMemoryHeap::Allocate(nSize, NULL, 0, Class()); } \
void operator delete[](void * ptr) \
{ PMemoryHeap::Deallocate(ptr, Class()); } \
PSPECIAL_DELETE_FUNCTION
inline void * operator new(size_t nSize, const char * file, int line)
{ return PMemoryHeap::Allocate(nSize, file, line, NULL); }
inline void * operator new[](size_t nSize, const char * file, int line)
{ return PMemoryHeap::Allocate(nSize, file, line, NULL); }
#ifndef __GNUC__
void * operator new(size_t nSize);
void * operator new[](size_t nSize);
void operator delete(void * ptr);
void operator delete[](void * ptr);
#if defined(_MSC_VER) && _MSC_VER>=1200
inline void operator delete(void * ptr, const char *, int)
{ PMemoryHeap::Deallocate(ptr, NULL); }
inline void operator delete[](void * ptr, const char *, int)
{ PMemoryHeap::Deallocate(ptr, NULL); }
#endif
#endif
class PMemoryHeapIgnoreAllocationsForScope {
public:
PMemoryHeapIgnoreAllocationsForScope() : previousIgnoreAllocations(PMemoryHeap::SetIgnoreAllocations(true)) { }
~PMemoryHeapIgnoreAllocationsForScope() { PMemoryHeap::SetIgnoreAllocations(previousIgnoreAllocations); }
private:
PBoolean previousIgnoreAllocations;
};
#define PMEMORY_IGNORE_ALLOCATIONS_FOR_SCOPE PMemoryHeapIgnoreAllocationsForScope instance_PMemoryHeapIgnoreAllocationsForScope
class PMemoryAllocationBreakpoint {
public:
PMemoryAllocationBreakpoint(DWORD point)
{
PMemoryHeap::SetAllocationBreakpoint(point);
}
};
#define PMEMORY_ALLOCATION_BREAKPOINT(point) PMemoryAllocationBreakpoint PMemoryAllocationBreakpointInstance(point)
#else // PMEMORY_CHECK || (defined(_MSC_VER) && defined(_DEBUG))
#define PMEMORY_HEAP 0
#define PNEW new
#define PNEW_AND_DELETE_FUNCTIONS
#define runtime_malloc(s) malloc(s)
#define runtime_free(p) free(p)
#define PMEMORY_IGNORE_ALLOCATIONS_FOR_SCOPE
#define PMEMORY_ALLOCATION_BREAKPOINT(point)
#endif // PMEMORY_CHECK || (defined(_MSC_VER) && defined(_DEBUG))
/*
* Implement "construct on first use" paradigm
*/
template <class GnuAllocator, class Type>
struct PAllocatorTemplate
{
Type * allocate(size_t v)
{
return GetAllocator().allocate(v);
}
void deallocate(Type * p, size_t v)
{
GetAllocator().deallocate(p, v);
}
private:
static GnuAllocator & GetAllocator()
{
static GnuAllocator instance;
return instance;
}
};
#define GCC_VERSION (__GNUC__ * 10000 \
+ __GNUC_MINOR__ * 100 \
+ __GNUC_PATCHLEVEL__)
// Memory pooling allocators
#if defined(__GNUC__) && (GCC_VERSION > 40000) && !defined(P_MINGW) && !defined(P_MACOSX)
#include <ext/mt_allocator.h>
template <class Type> struct PFixedPoolAllocator : public PAllocatorTemplate<__gnu_cxx::__mt_alloc<Type>, Type> { };
template <class Type> struct PVariablePoolAllocator : public PAllocatorTemplate<__gnu_cxx::__mt_alloc<Type>, Type> { };
#else
template <class Type> struct PFixedPoolAllocator : public PAllocatorTemplate<std::allocator<Type>, Type> { };
template <class Type> struct PVariablePoolAllocator : public PAllocatorTemplate<std::allocator<Type>, Type> { };
#endif
#define PDECLARE_POOL_ALLOCATOR() \
void * operator new(size_t nSize); \
void * operator new(size_t nSize, const char * file, int line); \
void operator delete(void * ptr); \
void operator delete(void * ptr, const char *, int)
#define PDEFINE_POOL_ALLOCATOR(cls) \
static PFixedPoolAllocator<cls> cls##_allocator; \
void * cls::operator new(size_t) { return cls##_allocator.allocate(1); } \
void * cls::operator new(size_t, const char *, int) { return cls##_allocator.allocate(1); } \
void cls::operator delete(void * ptr) { cls##_allocator.deallocate((cls *)ptr, 1); } \
void cls::operator delete(void * ptr, const char *, int) { cls##_allocator.deallocate((cls *)ptr, 1); }
/** Declare all the standard PTLib class information.
This macro is used to provide the basic run-time typing capability needed
by the library. All descendent classes from the <code>PObject</code> class require
these functions for correct operation. Either use this macro or the
<code>#PDECLARE_CLASS</code> macro.
The use of the <code>#PDECLARE_CLASS</code> macro is no longer recommended for reasons
of compatibility with documentation systems.
*/
#define PCLASSINFO(cls, par) \
public: \
typedef cls P_thisClass; \
static inline const char * Class() \
{ return #cls; } \
virtual PBoolean InternalIsDescendant(const char * clsName) const \
{ return strcmp(clsName, cls::Class()) == 0 || par::InternalIsDescendant(clsName); } \
virtual const char * GetClass(unsigned ancestor = 0) const \
{ return ancestor > 0 ? par::GetClass(ancestor-1) : cls::Class(); } \
virtual PObject::Comparison CompareObjectMemoryDirect(const PObject & obj) const \
{ return PObject::InternalCompareObjectMemoryDirect(this, dynamic_cast<const cls *>(&obj), sizeof(cls)); } \
PNEW_AND_DELETE_FUNCTIONS
#if P_HAS_TYPEINFO
#define PIsDescendant(ptr, cls) (dynamic_cast<const cls *>(ptr) != NULL)
#define PIsDescendantStr(ptr, str) ((ptr)->InternalIsDescendant(str))
#define PRemoveConst(cls, ptr) (const_cast<cls*>(ptr))
#if P_USE_ASSERTS
template<class BaseClass> inline BaseClass * PAssertCast(BaseClass * obj, const char * file, int line)
{ if (obj == NULL) PAssertFunc(file, line, BaseClass::Class(), PInvalidCast); return obj; }
#define PDownCast(cls, ptr) PAssertCast<cls>(dynamic_cast<cls*>(ptr),__FILE__,__LINE__)
#else
#define PDownCast(cls, ptr) (dynamic_cast<cls*>(ptr))
#endif
#include <typeinfo>
#else // P_HAS_TYPEINFO
#define PIsDescendant(ptr, cls) ((ptr)->InternalIsDescendant(cls::Class()))
#define PIsDescendantStr(ptr, str) ((ptr)->InternalIsDescendant(str))
#define PRemoveConst(cls, ptr) ((cls*)(ptr))
#if P_USE_ASSERTS
template<class BaseClass> inline BaseClass * PAssertCast(PObject * obj, const char * file, int line)
{ if (obj->InternalIsDescendant(BaseClass::Class())) return (BaseClass *)obj; PAssertFunc(file, line, BaseClass::Class(), PInvalidCast); return NULL; }
#define PDownCast(cls, ptr) PAssertCast<cls>((ptr),__FILE__,__LINE__)
#else
#define PDownCast(cls, ptr) ((cls*)(ptr))
#endif
#endif // P_HAS_TYPEINFO
/** Declare a class with PWLib class information.
This macro is used to declare a new class with a single public ancestor. It
starts the class declaration and then uses the <code>#PCLASSINFO</code> macro to
get all the run-time type functions.
The use of this macro is no longer recommended for reasons of compatibility
with documentation systems.
*/
#define PDECLARE_CLASS(cls, par) class cls : public par { PCLASSINFO(cls, par)
#ifdef DOC_PLUS_PLUS
} Match previous opening brace in doc++
#endif
///////////////////////////////////////////////////////////////////////////////
// The root of all evil ... umm classes
/** Ultimate parent class for all objects in the class library.
This provides functionality provided to all classes, eg run-time types,
default comparison operations, simple stream I/O and serialisation support.
*/
class PObject {
protected:
/** Constructor for PObject, made protected so cannot ever create one on
its own.
*/
PObject() { }
public:
/* Destructor required to get the "virtual". A PObject really has nothing
to destroy.
*/
virtual ~PObject() { }
/**@name Run Time Type functions */
//@{
/** Get the name of the class as a C string. This is a static function which
returns the type of a specific class.
When comparing class names, always use the <code>strcmp()</code>
function rather than comparing pointers. The pointers are not
necessarily the same over compilation units depending on the compiler,
platform etc.
@return pointer to C string literal.
*/
static inline const char * Class() { return "PObject"; }
/** Get the current dynamic type of the object instance.
When comparing class names, always use the <code>strcmp()</code>
function rather than comparing pointers. The pointers are not
necessarily the same over compilation units depending on the compiler,
platform etc.
The <code>#PCLASSINFO</code> macro declares an override of this function for
the particular class. The user need not implement it.
@return pointer to C string literal.
*/
virtual const char * GetClass(unsigned ancestor = 0) const { return ancestor > 0 ? "" : Class(); }
PBoolean IsClass(const char * cls) const
{ return strcmp(cls, GetClass()) == 0; }
/** Determine if the dynamic type of the current instance is a descendent of
the specified class. The class name is usually provided by the
<code>Class()</code> static function of the desired class.
The <code>#PCLASSINFO</code> macro declares an override of this function for
the particular class. The user need not implement it.
@return true if object is descended from the class.
*/
virtual PBoolean InternalIsDescendant(
const char * clsName // Ancestor class name to compare against.
) const
{ return IsClass(clsName); }
//@}
/**@name Comparison functions */
//@{
/** Result of the comparison operation performed by the <code>Compare()</code>
function.
*/
enum Comparison {
LessThan = -1,
EqualTo = 0,
GreaterThan = 1
};
/** Compare the two objects and return their relative rank. This function is
usually overridden by descendent classes to yield the ranking according
to the semantics of the object.
The default function is to use the <code>CompareObjectMemoryDirect()</code>
function to do a byte wise memory comparison of the two objects.
@return
<code>LessThan</code>, <code>EqualTo</code> or <code>GreaterThan</code>
according to the relative rank of the objects.
*/
virtual Comparison Compare(
const PObject & obj // Object to compare against.
) const;
/** Determine the byte wise comparison of two objects. This is the default
comparison operation for objects that do not explicitly override the
<code>Compare()</code> function.
The <code>#PCLASSINFO</code> macro declares an override of this function for
the particular class. The user need not implement it.
@return
<code>LessThan</code>, <code>EqualTo</code> or <code>GreaterThan</code>
according to the result <code>memcpy()</code> function.
*/
virtual Comparison CompareObjectMemoryDirect(
const PObject & obj // Object to compare against.
) const;
/// Internal function caled from CompareObjectMemoryDirect()
static Comparison InternalCompareObjectMemoryDirect(
const PObject * obj1,
const PObject * obj2,
PINDEX size
);
/** Compare the two objects.
@return
true if objects are equal.
*/
bool operator==(
const PObject & obj // Object to compare against.
) const { return Compare(obj) == EqualTo; }
/** Compare the two objects.
@return
true if objects are not equal.
*/
bool operator!=(
const PObject & obj // Object to compare against.
) const { return Compare(obj) != EqualTo; }
/** Compare the two objects.
@return
true if objects are less than.
*/
bool operator<(
const PObject & obj // Object to compare against.
) const { return Compare(obj) == LessThan; }
/** Compare the two objects.
@return
true if objects are greater than.
*/
bool operator>(
const PObject & obj // Object to compare against.
) const { return Compare(obj) == GreaterThan; }
/** Compare the two objects.
@return
true if objects are less than or equal.
*/
bool operator<=(
const PObject & obj // Object to compare against.
) const { return Compare(obj) != GreaterThan; }
/** Compare the two objects.
@return
true if objects are greater than or equal.
*/
bool operator>=(
const PObject & obj // Object to compare against.
) const { return Compare(obj) != LessThan; }
//@}
/**@name I/O functions */
//@{
/** Output the contents of the object to the stream. The exact output is
dependent on the exact semantics of the descendent class. This is
primarily used by the standard <code>#operator<<</code> function.
The default behaviour is to print the class name.
*/
virtual void PrintOn(
ostream &strm // Stream to print the object into.
) const;
/** Input the contents of the object from the stream. The exact input is
dependent on the exact semantics of the descendent class. This is
primarily used by the standard function.
The default behaviour is to do nothing.
*/
virtual void ReadFrom(
istream &strm // Stream to read the objects contents from.
);
/** Global function for using the standard << operator on objects descended
from PObject. This simply calls the objects <code>PrintOn()</code> function.
@return the \p strm parameter.
*/
inline friend ostream & operator<<(
ostream &strm, ///< Stream to print the object into.
const PObject & obj ///< Object to print to the stream.
) { obj.PrintOn(strm); return strm; }
/** Global function for using the standard >> operator on objects descended
from PObject. This simply calls the objects <code>ReadFrom()</code> function.
@return the \p strm parameter.
*/
inline friend istream & operator>>(
istream &strm, ///< Stream to read the objects contents from.
PObject & obj ///< Object to read inormation into.
) { obj.ReadFrom(strm); return strm; }
/**@name Miscellaneous functions */
//@{
/** Create a copy of the class on the heap. The exact semantics of the
descendent class determine what is required to make a duplicate of the
instance. Not all classes can even \b do a clone operation.
The main user of the clone function is the <code>PDictionary</code> class as
it requires copies of the dictionary keys.
The default behaviour is for this function to assert.
@return
pointer to new copy of the class instance.
*/
virtual PObject * Clone() const;
/** This function yields a hash value required by the <code>PDictionary</code>
class. A descendent class that is required to be the key of a dictionary
should override this function. The precise values returned is dependent
on the semantics of the class. For example, the <code>PString</code> class
overrides it to provide a hash function for distinguishing text strings.
The default behaviour is to return the value zero.
@return
hash function value for class instance.
*/
virtual PINDEX HashFunction() const;
//@}
};
///////////////////////////////////////////////////////////////////////////////
// Platform independent types
// All these classes encapsulate primitive types such that they may be
// transfered in a platform independent manner. In particular it is used to
// do byte swapping for little endien and big endien processor architectures
// as well as accommodating structure packing rules for memory structures.
#define PANSI_CHAR 1
#define PLITTLE_ENDIAN 2
#define PBIG_ENDIAN 3
template <typename type>
struct PIntSameOrder {
__inline PIntSameOrder() : data(0) { }
__inline PIntSameOrder(type value) : data(value) { }
__inline PIntSameOrder(const PIntSameOrder & value) : data(value.data) { }
__inline PIntSameOrder & operator=(type value) { data = value; return *this; }
__inline PIntSameOrder & operator=(const PIntSameOrder & value) { data = value.data; return *this; }
__inline operator type() const { return data; }
__inline friend ostream & operator<<(ostream & s, const PIntSameOrder & v) { return s << v.data; }
__inline friend istream & operator>>(istream & s, PIntSameOrder & v) { return s >> v.data; }
private:
type data;
};
template <typename type>
struct PIntReversedOrder {
__inline PIntReversedOrder() : data(0) { }
__inline PIntReversedOrder(type value) { ReverseBytes(value, data); }
__inline PIntReversedOrder(const PIntReversedOrder & value) : data(value.data) { }
__inline PIntReversedOrder & operator=(type value) { ReverseBytes(value, data); return *this; }
__inline PIntReversedOrder & operator=(const PIntReversedOrder & value) { data = value.data; return *this; }
__inline operator type() const { type value; ReverseBytes(data, value); return value; }
__inline friend ostream & operator<<(ostream & s, const PIntReversedOrder & value) { return s << (type)value; }
__inline friend istream & operator>>(istream & s, PIntReversedOrder & v) { type val; s >> val; v = val; return s; }
private:
type data;
static __inline void ReverseBytes(const type & src, type & dst)
{
size_t s = sizeof(type)-1;
for (size_t d = 0; d < sizeof(type); ++d,--s)
((BYTE *)&dst)[d] = ((const BYTE *)&src)[s];
}
};
#ifndef PCHAR8
#define PCHAR8 PANSI_CHAR
#endif
#if PCHAR8==PANSI_CHAR
typedef PIntSameOrder<char> PChar8;
#endif
typedef PIntSameOrder<char> PInt8;
typedef PIntSameOrder<unsigned char> PUInt8;
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntSameOrder<PInt16> PInt16l;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntReversedOrder<PInt16> PInt16l;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntReversedOrder<PInt16> PInt16b;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntSameOrder<PInt16> PInt16b;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntSameOrder<WORD> PUInt16l;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntReversedOrder<WORD> PUInt16l;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntReversedOrder<WORD> PUInt16b;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntSameOrder<WORD> PUInt16b;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntSameOrder<PInt32> PInt32l;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntReversedOrder<PInt32> PInt32l;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntReversedOrder<PInt32> PInt32b;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntSameOrder<PInt32> PInt32b;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntSameOrder<DWORD> PUInt32l;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntReversedOrder<DWORD> PUInt32l;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntReversedOrder<DWORD> PUInt32b;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntSameOrder<DWORD> PUInt32b;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntSameOrder<PInt64> PInt64l;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntReversedOrder<PInt64> PInt64l;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntReversedOrder<PInt64> PInt64b;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntSameOrder<PInt64> PInt64b;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntSameOrder<PUInt64> PUInt64l;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntReversedOrder<PUInt64> PUInt64l;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntReversedOrder<PUInt64> PUInt64b;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntSameOrder<PUInt64> PUInt64b;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntSameOrder<float> PFloat32l;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntReversedOrder<float> PFloat32l;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntReversedOrder<float> PFloat32b;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntSameOrder<float> PFloat32b;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntSameOrder<double> PFloat64l;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntReversedOrder<double> PFloat64l;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntReversedOrder<double> PFloat64b;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntSameOrder<double> PFloat64b;
#endif
#ifndef NO_LONG_DOUBLE // stupid OSX compiler
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntSameOrder<long double> PFloat80l;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntReversedOrder<long double> PFloat80l;
#endif
#if PBYTE_ORDER==PLITTLE_ENDIAN
typedef PIntReversedOrder<long double> PFloat80b;
#elif PBYTE_ORDER==PBIG_ENDIAN
typedef PIntSameOrder<long double> PFloat80b;
#endif
#endif
///////////////////////////////////////////////////////////////////////////////
// Miscellaneous
/*$MACRO PARRAYSIZE(array)
This macro is used to calculate the number of array elements in a static
array.
*/
#define PARRAYSIZE(array) ((PINDEX)(sizeof(array)/sizeof(array[0])))
/*$MACRO PMIN(v1, v2)
This macro is used to calculate the minimum of two values. As this is a
macro the expression in <code>v1</code> or <code>v2</code> is executed
twice so extreme care should be made in its use.
*/
#define PMIN(v1, v2) ((v1) < (v2) ? (v1) : (v2))
/*$MACRO PMAX(v1, v2)
This macro is used to calculate the maximum of two values. As this is a
macro the expression in <code>v1</code> or <code>v2</code> is executed
twice so extreme care should be made in its use.
*/
#define PMAX(v1, v2) ((v1) > (v2) ? (v1) : (v2))
/*$MACRO PABS(val)
This macro is used to calculate an absolute value. As this is a macro the
expression in <code>val</code> is executed twice so extreme care should be
made in its use.
*/
#define PABS(v) ((v) < 0 ? -(v) : (v))
#endif // PTLIB_OBJECT_H
// End Of File ///////////////////////////////////////////////////////////////
More information about the Pkg-voip-maintainers
mailing list