Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!pasteur!ucbvax!ulysses!cjc
From: cjc@ulysses.homer.nj.att.com (Chris Calabrese[rs])
Newsgroups: comp.lang.c
Subject: Re: sizeof(function) - preproposal survey
Message-ID: <10076@ulysses.homer.nj.att.com>
Date: 15 Feb 88 16:17:59 GMT
References: <11801@brl-adm.ARPA>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 25
Summary: how is this possible?

In article <11801@brl-adm.ARPA>, LINNDR%VUENGVAX.BITNET@CUNYVM.CUNY.EDU writes:
> I need some help from the readers of comp.lang.c/info-c in preparation
> for making a proposal to X3J11. The gist of my proposal is that the
> sizeof operator, when applied to a function name, would return the
> length of the function rather than the size of a pointer to a function.

How is this possible?  how can the length of a function be determined at
compile time without having compile all the functions dependant upon
the function under consideration first?

What happens when they're in two different files and get compiled
seperately?  What happens if two functions are dependent upon
each other for size information?

Somebody tell me how this is possible?

Another, more interesting possibility is that sizeof return the number
of arguments which the function takes.

Of course, what do we do with the C programs which already use
the current meaning of the sizeof operator on functions?

	Chris Calabrese
	AT&T Bell Labs
	ulysses!cjc