Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!psuvm!uh2
From: UH2@psuvm.psu.edu (Lee Sailer)
Newsgroups: comp.sys.amiga.programmer
Subject: RE: HEEELLLPPPPPP!!!!!
Message-ID: <91158.180019UH2@psuvm.psu.edu>
Date: 7 Jun 91 22:00:19 GMT
References: <9106060516.AA18295@bruny.cc.utas.edu.au>
Organization: Penn State University
Lines: 15

> There is an easy way to fix it - include

>char *malloc();

> in the begining of the program.

Aaahhhh.  Of course.

Anyway, I've noticed that Borland C++ considers a function that
doesn't have a prototype to be an error.  Thus, this type of
programmer error (it isn't really a bug, in C Classic) cannot
occur.  It ought to be at least a warning, anyway.  I think
that the ANSI C standard requires it to be either an error or a warning.

lee