🚀 go-pugleaf

In article <19921217111545SEB1525@MVS.draper.com> SEB1525@MVS.draper.com (Steve Bacher) writes:
>In article <tmi3iac@sgi.sgi.com>,
>davea@quasar.mti.sgi.com (David B.Anderson) writes:
[ ]
>>Brendan is quite right.  And it _is_ probably simplest to use gcc alloca.c
[ ]
>I weighed grabbing alloca.c out of the gcc or emacs distribution.  But
>this alloca requires a function xmalloc() to be defined.  Why not just
[ ]
>Do you have to change xmalloc to malloc, or define xmalloc to be
>malloc in the compile?

This question has arisen several times in the last year because the
source to alloca.c does not describe xmalloc.  xmalloc is simply a malloc
wrapper that guarantees it will never return 0.

#include <stdio.h>
#include <malloc.h>
#include <stdlib.h>
void *xmalloc(unsigned size)
{
  void *val;

  val = malloc(size);
  if(val == 0) {
    fprintf(stderr, "Oops! malloc on %lu bytes returned 0.\n", 
	(unsigned long)size);
    exit(EXIT_FAILURE);
  }
  return val;
}

Regards,
[ David B. Anderson             (415)390-4263             davea@sgi.com ]