Lines Matching full:with

40 with NDEBUG defined, yielding a version of BGET with  minimal  size  and
73 allocated.   Machines  with  a  linear address architecture, such as the
78 GETTING STARTED WITH BGET
82 three basic ways of working with BGET.  The  functions  mentioned  below
93 environment,  simply  call  bpool() with the start address and length of
94 the buffer pool area in RAM,  then  allocate  buffers  with  bget()  and
95 release  them  with brel().  Embedded applications with very limited RAM
104 program),  or  otherwise  unsuitable,  you  can  replace  it  with BGET.
105 Initially  define  a  buffer  pool   of   an   appropriate   size   with
107 low-level memory allocator.  Then allocate buffers with bget(), bgetz(),
110 compatibility  with  C  library  functions).  Release buffers by calling
120 application-specific memory compaction by compiling BGET with the  BECtl
126 defined with bectl(), you simply use bget() and brel() to  allocate  and
127 release  storage  as before.  You can supply an initial buffer pool with
130 compaction function has been supplied.  If so, it is  called  (with  the
136 if  it  fails  again,  call  the  compaction  function  again  with  the
142 function is called  with  an  argument  indicating  how  many  bytes  of
154 Equipped with appropriate allocation, release, and compaction functions,
208 request fails, the <compact> function  will  be  called  with  arguments
229 being  reallocated  with bgetr() would lead to disaster.  Implementing a
255 <nget>  and  <nrel>  are  filled,  respectively,  with  the  number   of
267 variables pointed to  by  <npget>  and  <nprel>  will  be  filled  with,
270 will be filled with the number of bget() and brel() calls, respectively,
288 validated  for  bad  pointers,  overwritten  data,  etc.  If compiled with