godzil/tack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

removed the limitation of the next field

Browse Source
This commit is contained in:
ceriel
1987-08-03 09:07:25 +00:00
parent 5e715448e3
commit c158bf75de
4 changed files with 28 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
modules/src/alloc/alloc.3
View File

@@ -67,8 +67,7 @@ All these routines use \fImalloc\fR and \fIrealloc\fR.
\fIFree\fR can be used on pointers returned by these routines.
.PP
\fISt_alloc\fR and \fIst_free\fR provide a mechanism for maintaining free lists
of structures, whose first field is a pointer called \fBnext\fR.
This field is used to chain free structures together.
of structures.
\fISt_alloc\fR takes three parameters: \fIphead\fR is a pointer to a field
containing the head of the free list, \fIsize\fR contains the size of the
structures, and \fIcount\fR indicates how many new structures must be allocated
@@ -93,3 +92,12 @@ malloc(3)
call a routine \fINo_Mem\fR if there is no memory available. This routine
is not supposed to return. A default one, that
gives an error message and stops execution, is provided.
.SH BUGS
The
.I st_alloc
mechanism only works for structures that are large enough to contain one
pointer.
Also,
.I st_free
actually is a macro, and references its arguments more than once, so they
better not have side-effects.