Mail Archives: djgpp/2001/09/29/16:19:14
Alright you acronymizers, GREP?
Have no idea yet where to relocate the 'C Standard', done been eight years
since I last coded, now I find myself in a bit of a crunch because I needs
to create a com port driven version of a SB recording/playback program I
found out there, mainly,
S B 1 6 S o u n d Written by Ethan Brodsky
Copyright 1995 by Ethan Brodsky. All rights reserved.
Did locate a disk which contained Borland C/C++, in ALLOC.H:
void _FAR *_Cdecl calloc(size_t __nitems, size_t __size);
void _Cdecl free(void _FAR *__block);
void _FAR *_Cdecl malloc(size_t __size);
void _FAR *_Cdecl realloc(void _FAR *__block, size_t __size);
So, in the below header, I comment out the unused include;
#include <alloc.h>
#include <conio.h>
#include <dos.h>
#include <mem.h>
#include <stdlib.h>
using Rhide, Make, and I get this:
sbio.c(78) Error: parse error before `*'
sbio.c(78) Error: `interrupt' declared as function returning a function
sbio.c(78) Error: function `interrupt' is initialized like a variable
sbio.c(247) Error: parse error before `inthandler'
(78) void interrupt (*oldintvector)() = NULL;
"Les Cargill" <lcargill AT worldnet DOT att DOT net> wrote in message
news:3BB5FAAD DOT AB8B09C1 AT worldnet DOT att DOT net...
> CBFalconer wrote:
> > Les Cargill wrote:
> > > cwg wrote:
> > > > it's in the turbo-c project i'm working on.
> > > > what would be the djgpp replacement?
> > > Possibly <malloc.h>? grep is our friend...
> > No, it is in <stdlib.h>. The C standard is your friend.
> If he was interested in the 'C' standard, he would have looked there
> first.
>
> Just to be persnickety, he asked about <alloh.h>. There are things
> declared there other than malloc(). There is probably no direct
> <alloc.h> replacement in GNU. I don't know. Never had to ask the
> question before.
>
> I also noticed, in the Borland <malloc.h> , this:
> File MALLOC.H:
> /* malloc.h
> #if !defined(__MALLOC_H)
> #define __MALLOC_H
> #if !defined(__ALLOC_H)
> #include <alloc.h>
>
>
> Borland's <alloc.h> is sorta disjoint from
> the GNU usual stuff. malloc() does get prototyped in both
> places in Borland. There are other malloc() variants, and
> more of them appear in <malloc.h> than in <stdlib.h> . I always
> disliked that - it should appear in one place.
>
> In general, my preferred method of resolving includes when porting
> to an unfmailiar environment is to remove the offending include,
> making sure -Wall(or equivalent) is on, and making a list of all
> the prototype errors.
>
> grep for those, then massage until warnings disappear.
>
>
> > --
> > Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT XXXXworldnet DOT att DOT net)
> > (Remove "XXXX" from reply address. yahoo works unmodified)
> > mailto:uce AT ftc DOT gov (for spambots to harvest)
>
> --
> http://home.att.net/~lcargill
- Raw text -