source: trunk/src/binutils/include/objalloc.h@ 1790

Last change on this file since 1790 was 610, checked in by bird, 22 years ago

This commit was generated by cvs2svn to compensate for changes in r609,
which included commits to RCS files with non-trunk default branches.

  • Property cvs2svn:cvs-rev set to 1.1.1.2
  • Property svn:eol-style set to native
  • Property svn:executable set to *
File size: 3.9 KB
Line 
1/* objalloc.h -- routines to allocate memory for objects
2 Copyright 1997, 2001 Free Software Foundation, Inc.
3 Written by Ian Lance Taylor, Cygnus Solutions.
4
5This program is free software; you can redistribute it and/or modify it
6under the terms of the GNU General Public License as published by the
7Free Software Foundation; either version 2, or (at your option) any
8later version.
9
10This program is distributed in the hope that it will be useful,
11but WITHOUT ANY WARRANTY; without even the implied warranty of
12MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
13GNU General Public License for more details.
14
15You should have received a copy of the GNU General Public License
16along with this program; if not, write to the Free Software
17Foundation, 59 Temple Place - Suite 330,
18Boston, MA 02111-1307, USA. */
19
20#ifndef OBJALLOC_H
21#define OBJALLOC_H
22
23#include "ansidecl.h"
24
25/* These routines allocate space for an object. The assumption is
26 that the object will want to allocate space as it goes along, but
27 will never want to free any particular block. There is a function
28 to free a block, which also frees all more recently allocated
29 blocks. There is also a function to free all the allocated space.
30
31 This is essentially a specialization of obstacks. The main
32 difference is that a block may not be allocated a bit at a time.
33 Another difference is that these routines are always built on top
34 of malloc, and always pass an malloc failure back to the caller,
35 unlike more recent versions of obstacks. */
36
37/* This is what an objalloc structure looks like. Callers should not
38 refer to these fields, nor should they allocate these structure
39 themselves. Instead, they should only create them via