This file is indexed.

/usr/include/pi-buffer.h is in libpisock-dev 0.12.5-dfsg-2build2.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
/*
 * $Id: pi-buffer.h,v 1.6 2006/10/17 13:24:06 desrod Exp $
 *
 * pi-buffer.h:  simple data block management for variable data storage
 *
 * Copyright (c) 2004-2005, Florent Pillet.
 *
 * This library is free software; you can redistribute it and/or modify it
 * under the terms of the GNU Library General Public License as published by
 * the Free Software Foundation; either version 2 of the License, or (at
 * your option) any later version.
 *
 * This library is distributed in the hope that it will be useful, but
 * WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Library
 * General Public License for more details.
 *
 * You should have received a copy of the GNU Library General Public License
 * along with this library; if not, write to the Free Software Foundation,
 * * Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. 
 */

/** @file pi-buffer.h
 *  @brief Variable size buffer management interface
 *  @author Florent Pillet
 *
 * pi-buffer provides for a reliable and easy to use variable size buffer
 * management, allowing for buffers that grow as needed to store
 * variable-length data.
 *
 * When you create a buffer with pi_buffer_new(), you indicate an initial
 * capacity that is allocated. The number of used bytes is set to 0. To
 * append data to the buffer, use pi_buffer_append(). This ensures that the
 * buffer grows as needed.
 *
 * You can access data in the buffer using the @a buffer->data member. The
 * number of bytes used is always accessible using @a buffer->used.
 *
 * It is possible to use the pi-buffer functions on static buffers. In this
 * case, you won't call pi_buffer_free() on the structure. You'll dispose of
 * the memory yourself instead. Here is an example:
 *
 * @code
 *	pi_buffer_t mybuf;
 *	mybuf.data = (unsigned char *) malloc(256);
 *	mybuf.allocated = 256;
 *	mybuf.used = 0;
 *
 *	// ... perform your tasks here ....
 *	pi_buffer_append(&mybuf, somedata, somedatasize);
 *	// ...
 *
 *	free(mybuf.data);
 * @endcode
 */

#ifndef _PILOT_BUFFER_H_
#define _PILOT_BUFFER_H_

#include "pi-args.h"

#ifdef __cplusplus
extern "C" {
#endif
	/** @brief Variable buffer structure */
	typedef struct pi_buffer_t {
		unsigned char *data;	/**< Pointer to the data */
		size_t allocated;	/**< Number of bytes allocated */
		size_t used;		/**< Number of allocated bytes actually used */
	} pi_buffer_t;

	/** @brief Create a new variable size buffer
	 *
	 * Dispose of this buffer with pi_buffer_free()
	 *
	 * @param capacity Initial size to allocate
	 * @return A newly allocated pi_buffer_t structure
	 */
	extern pi_buffer_t* pi_buffer_new
		PI_ARGS((size_t capacity));
	
	/** @brief Ensure the buffer is large enough to store @p capacity bytes of data
	 *
	 * This grows the allocated buffer as needed and updates the @a allocated
	 * member. Doesn't touch the @a used member. After this call succeeds, you
	 * can directly use the @a buffer->data pointer to store up to
	 * @a buffer->allocated bytes using direct memory access.
	 *
	 * @param buf The buffer to grow
	 * @param new_capacity The total number of bytes the buffer is expected to contain
	 * @return The @p buf buffer on success, NULL if a memory error happened
	 */
	extern pi_buffer_t* pi_buffer_expect
		PI_ARGS((pi_buffer_t *buf, size_t new_capacity));

	/** @brief Append data to the buffer
	 *
	 * Grow the buffer if needed.
	 *
	 * @param buf The buffer to grow
	 * @param data Pointer to the data to append
	 * @param len Length of the data to append
	 * @return The @p buf buffer on success, NULL if a memory error happened
	 */
	extern pi_buffer_t* pi_buffer_append
		PI_ARGS((pi_buffer_t *buf, PI_CONST void *data, size_t len));

	/** @brief Append a buffer to another buffer
	 *
	 * @param dest The buffer to append to
	 * @param src Buffer whose data will be appended to @p dest
	 * @return The @p dest buffer on success, NULL if a memory error happened
	 */
	extern pi_buffer_t* pi_buffer_append_buffer
		PI_ARGS((pi_buffer_t *dest, PI_CONST pi_buffer_t *src));

	/** @brief Reset the @a used member of a buffer
	 *
	 * The @p used member is set to 0. If the actual allocated bytes is large,
	 * the allocation may shrink to a reasonable value to prevent unneeded
	 * memory use.
	 *
	 * @param buf The buffer to clear
	 * @return The @p buf parameter
	 */
	extern void pi_buffer_clear
		PI_ARGS((pi_buffer_t *buf));

	/** @brief Dispose of all memory used by a buffer allocated with pi_buffer_new()
	 *
	 * After this call, the @p buf structure itself will have been freed as well.
	 * Do not reuse the pointer.
	 *
	 * @param buf The buffer to dispose of
	 */
	extern void pi_buffer_free
		PI_ARGS((pi_buffer_t *buf));

#ifdef __cplusplus
}
#endif

#endif