From: Erik Max Francis <max AT alcyone DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: size of a function in memory
Date: Sat, 14 Nov 1998 13:40:50 -0800
Organization: Alcyone Systems
Lines: 20
Message-ID: <364DF8E2.4266297@alcyone.com>
References: <19981112170856 DOT 18464 DOT 00000989 AT ng-fi1 DOT aol DOT com> <3KL22.2159$vl4 DOT 1265858 AT tundra DOT ops DOT attcanada DOT net> <364DEBDA DOT 928C79F2 AT cartsys DOT com>
NNTP-Posting-Host: charmaine.alcyone.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01 (X11; I; Linux 2.0.34 i686)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Nate Eldredge wrote:

> Be aware that this is not portable.  It depends fairly strongly on
> GCC's
> compiling conventions and may fail on other compilers, or even some
> future version of GCC.  If it's for something like memory locking that
> isn't portable anyway, though, this probably isn't much of an issue.

I can't imagine why anyone would need to know the size of a function
unless they were already planning on doing something extremely
nonportable.

-- 
Erik Max Francis / email max AT alcyone DOT com / whois mf303 / icq 16063900
Alcyone Systems / irc maxxon (efnet) / finger max AT sade DOT alcyone DOT com
  San Jose, CA / languages En, Eo / web http://www.alcyone.com/max/
          USA / icbm 37 20 07 N 121 53 38 W / &tSftDotIotE
             \
            / The pure and simple truth is rarely pure and never simple.
           / Oscar Wilde