Apache HTTPD
Macros | Functions | Variables
apr_base64.c File Reference
#include <assert.h>
#include "apr_base64.h"

Go to the source code of this file.

Macros

#define APR_BASE64_ENCODE_MAX   1610612733
 
#define APR_BASE64_DECODE_MAX   2863311524u
 

Functions

 APU_DECLARE (int)
 

Variables

static const unsigned char pr2six [256]
 
static const char basis_64 []
 

Macro Definition Documentation

◆ APR_BASE64_DECODE_MAX

#define APR_BASE64_DECODE_MAX   2863311524u

Definition at line 35 of file apr_base64.c.

◆ APR_BASE64_ENCODE_MAX

#define APR_BASE64_ENCODE_MAX   1610612733

Definition at line 32 of file apr_base64.c.

Function Documentation

◆ APU_DECLARE()

APU_DECLARE ( int  )

Most DBM libraries take a POSIX mode for creating files. Don't trust the mode_t type, some platforms may not support it, int is safe.

< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.

< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.

< Exclusive lock. Only one process may hold an exclusive lock at any given time. This is analogous to a "write lock".

< Exclusive lock. Only one process may hold an exclusive lock at any given time. This is analogous to a "write lock".

< Replace

< Insert with duplicates

< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.

< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.

< mask to extract lock type

< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.

< Exclusive lock. Only one process may hold an exclusive lock at any given time. This is analogous to a "write lock".

< Exclusive lock. Only one process may hold an exclusive lock at any given time. This is analogous to a "write lock".

< Size of the file

< Shared lock. More than one process or thread can hold a shared lock at any given time. Essentially, this is a "read lock", preventing writers from establishing an exclusive lock.

< Exclusive lock. Only one process may hold an exclusive lock at any given time. This is analogous to a "write lock".

Definition at line 119 of file apr_base64.c.

Variable Documentation

◆ basis_64

const char basis_64[]
static
Initial value:
=
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/"

Definition at line 193 of file apr_base64.c.

◆ pr2six

const unsigned char pr2six[256]
static

Definition at line 38 of file apr_base64.c.