Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!tcdcs!swift.cs.tcd.ie!maths.tcd.ie!tim
From: tim@maths.tcd.ie (Timothy Murphy)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK C library & opening files - HELP!?!
Message-ID: <1990Sep3.223651.7921@maths.tcd.ie>
Date: 3 Sep 90 22:36:51 GMT
References: <12866@june.cs.washington.edu> <9898@goofy.Apple.COM>
Organization: Dept. of Maths, Trinity College, Dublin, Ireland.
Lines: 40

On a related topic, what is the convention for naming paths in THINK C?
I find I can open a 'cousin' file as "::pa_dir:cousin_dir:file"
but if I want to give the full path,
must I know the name of the (hard) disk?

Another question: is there any way of #defining outside the program --
as eg from the command line in Unix or MS-DOS
cc -Dxyz prog.c

While I've got your attention,
is the 32k data limit due to Mac internals,
or to THINK C?

Last question (for the moment):
I find malloc()...free()
doesn't actually free the space the *first* time it is called,
but does on subsequent occasions.
Has anyone else noticed this?
Eg

#include <stdio.h>
#include <stdlib.h>
main()
{
  int i;
  char *cp;
  for (i=0; i<100; i++) {
    cp = malloc(1000);
    printf("cp = %p\n", cp);
    free(cp);
  }
}

Timothy Murphy <tim@maths.tcd.ie>

-- 

Timothy Murphy  

e-mail: tim@maths.tcd.ie