Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.16 $; site inmet.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!gatech!seismo!lll-crg!ucdavis!ucbvax!decvax!cca!inmet!bhyde
From: bhyde@inmet.UUCP
Newsgroups: net.micro.mac
Subject: Re: Using the Macintosh Toolbox with C (
Message-ID: <26700045@inmet.UUCP>
Date: Sat, 30-Nov-85 15:07:00 EST
Article-I.D.: inmet.26700045
Posted: Sat Nov 30 15:07:00 1985
Date-Received: Thu, 5-Dec-85 06:29:30 EST
References: <3021@sun.UUCP>
Lines: 19
Nf-ID: #R:sun:-302100:inmet:26700045:000:832
Nf-From: inmet!bhyde    Nov 30 15:07:00 1985


It is nice to have some technical discussion in this silly news group.

Another case that gives the shakes to C compilers is when you have 
snarfed a pointer to a pascal subprogram out of some data structure.
The cases I'm familar with, having written glue to handle them,
are filtering calls to the bottle neck procedures or to control
def procs.  Such a filter wants to spend a few moments considering
the call and then just let the real procedure handle the normal
case.

One plausable solution in the Megamax tradition would be to allow
the "pascal" modifier to be placed on procedure variable declarations.

In some cases you can avoid assembler language in such cases by using
your C compiler's willingness to pass structure values.  This is done
by writing a structure that mimics the Pascal call site.

ben hyde, cambridge.