Path: utzoo!attcan!uunet!husc6!bu.edu!nntp-read!quack
From: quack@bucsf.bu.edu (Rajeev Dayal)
Newsgroups: comp.sys.apple
Subject: HyperC questions...
Message-ID: <QUACK.90Feb21115819@bucsf.bu.edu>
Date: 21 Feb 90 16:58:19 GMT
Sender: news@bu.edu.bu.edu
Distribution: comp.sys.apple
Organization: Boston Univ., Computer Science
Lines: 39


Well...here goes...

How do you get the current working directory?  Is there some kind of call
that we can use?  Something like char *getwd()?

The floating point functions are essentially unusable in their current
form.  This is because any call to, for example, multiply two floating pt.
numbers does not return the value, but puts the value into one of the
parameters passed into this call.  Like, fmuld(floatdest, float) puts the
double result into the variable floatdest.  I was wondering if anyone knew the
overhead in calling separate functions, because I was hoping to do
something like:
DOUBLE multd (f1, f2)
	DOUBLE f1, f2;
{
	DOUBLE temp;

	temp = f1;  /* I'm not sure that this will work, since doubles */
		    /* are stored as strings, may need a strcpy, or  */
		    /* god knows what else */
	return (fmuld (temp, f2));
}

I was thinking about defining lots of these functions, compiling to object
files and just linking them with the files that I would use them with.  I'd
have to create header files, but that would be no problem.  The only real
problem would be running out of space because of all these funtions.

This is why I wanted to ask if anyone knows how much does time is wasted by
HyperC in creating the activation record for the new function, and
allocating space for the new variable...

This is the only fix that I can think of to make the floating pt. libraries
more usable.  Am I missing something obvious?  Is there a way to make a
#define statement do this?  Or are the values passed back, and am I just
assuming that they aren't?

-Rajeev