c64bb6850c
ircd::net: Add an is_null(ipport/ipaddr). ircd::net: Improve the v6/v4 check efficiency. ircd::net: Swap defaulting from v6 to v4 for better null address output. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| allocator.cc | ||
| allocator_gnu.cc | ||
| allocator_je.cc | ||
| assert.cc | ||
| base.cc | ||
| client.cc | ||
| conf.cc | ||
| crh.cc | ||
| ctx.cc | ||
| ctx.h | ||
| ctx_eh.cc | ||
| ctx_ole.cc | ||
| db.cc | ||
| db.h | ||
| db_database.h | ||
| db_env.cc | ||
| db_env.h | ||
| db_env_state.h | ||
| db_port.cc | ||
| db_port.h | ||
| db_write_thread.cc | ||
| demangle.cc | ||
| exception.cc | ||
| fmt.cc | ||
| fs.cc | ||
| fs_aio.cc | ||
| fs_aio.h | ||
| globular.cc | ||
| http.cc | ||
| http2.cc | ||
| info.cc | ||
| ios.cc | ||
| ircd.cc | ||
| js.cc | ||
| json.cc | ||
| lex_cast.cc | ||
| locale.cc | ||
| logger.cc | ||
| m.cc | ||
| m_dbs.cc | ||
| m_event.cc | ||
| m_fed.cc | ||
| m_id.cc | ||
| m_name.cc | ||
| m_room.cc | ||
| magic.cc | ||
| Makefile.am | ||
| mods.cc | ||
| mods.h | ||
| mods_ldso.cc | ||
| net.cc | ||
| openssl.cc | ||
| parse.cc | ||
| prof.cc | ||
| prof_linux.cc | ||
| rand.cc | ||
| README.md | ||
| resource.cc | ||
| rfc1035.cc | ||
| rfc1459.cc | ||
| rfc3986.cc | ||
| server.cc | ||
| sodium.cc | ||
| stats.cc | ||
| stringops.cc | ||
| timedate.cc | ||
| tokens.cc | ||
| util.cc | ||
| vg.cc | ||
IRCd Library Definitions
This directory contains definitions and linkage for libircd
The purpose of libircd is to facilitate the execution of a server which
handles requests from end-users. The library hosts a set of pluggable modules
which may introduce the actual application features (or the "business logic")
of the server.
Implied #include <ircd.h>
The ircd.h standard include group
is pre-compiled and included first by default for every compilation unit in
this directory. Developers do not have to worry about including project headers
in a compilation unit, especially when creating and reorganizing either of them.
Note that because ircd.h is include above any manually included header,
there is a theoretical possibility for a conflict. We make a serious effort
to prevent ircd.h from introducing pollution outside of our very specific
namespaces (see: Project Namespaces).
Dependency Isolation
Compilation units are primarily divided around the inclusion of a specific
header or third-party dependency which is not involved in the
ircd.h include group. Second to that, units
tend to be divided by namespace and the subsystem they're implementing. Units
can further be divided if they become unwieldy, but we bias toward large aggregate
units. Within these large units, there are divisions which group the definitions
by the include/ircd/ header which declares them.
We do not included third-party headers in our own headers
which are included by others. A developer of an ircd:: interface can choose
to either forward declare third-party symbols in our headers, or wrap more
complicated functionality.