nested procedures and the C language

[Neil Zanella]

Hello,

I am curious as to why the designers of C did not include support for
Pascal-like nested procedures. I guess that it's because nested procedures
in C would not buy you much other than marginally cleaner namespaces, and
then again C has a static keyword for limiting the scope of functions to
a file, which is not quite the same, but seems enough for all practical
purposes. Anyone care to either agree or disagree?

Regards,

Neil

[Grumble]

Neil Zanella wrote:

I am curious as to why the designers of C did not include support for
Pascal-like nested procedures. I guess that it's because nested procedures
in C would not buy you much other than marginally cleaner namespaces, and
then again C has a static keyword for limiting the scope of functions to
a file, which is not quite the same, but seems enough for all practical
purposes. Anyone care to either agree or disagree?

This is Frequently Asked Question number 20.24

http://www.eskimo.com/~scs/C-faq/q20.24.html

[Keith Thompson]

Neil Zanella <nz******@cs.mu n.ca> writes:

I am curious as to why the designers of C did not include support for
Pascal-like nested procedures. I guess that it's because nested procedures
in C would not buy you much other than marginally cleaner namespaces, and
then again C has a static keyword for limiting the scope of functions to
a file, which is not quite the same, but seems enough for all practical
purposes. Anyone care to either agree or disagree?

I suspect part of the reason is that disallowing nested procedures
makes the compiler's job easier, something that was probably more
important when the language was being designed than it is now. The
problem is references to variables in enclosing procedures. For
example (in hypothetical C syntax):

void outer(void)
{
int outer_var = 1;

void inner(void)
{
int inner_var = outer_var;
}
}

Assuming a stack implementation, the reference to outer_var in inner()
requires digging some variable distance down the stack, depending on
the current state of the call stack. (Imagine that inner() is
recursive.)

I think Algol supports nested procedures so there was precedent for
the idea, but it wasn't thought to be worth the extra effort.

--
Keith Thompson (The_Other_Keit h) ks*@cts.com <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://www.sdsc.edu/~kst>
Schroedinger does Shakespeare: "To be *and* not to be"

[Derk Gwen]

# I am curious as to why the designers of C did not include support for
# Pascal-like nested procedures. I guess that it's because nested procedures
# in C would not buy you much other than marginally cleaner namespaces, and
# then again C has a static keyword for limiting the scope of functions to
# a file, which is not quite the same, but seems enough for all practical
# purposes. Anyone care to either agree or disagree?

Because Fortran didn't. C is mixture of Fortran and Jovial and a sprinkling
of Algol 68. The stack display and static link were well understood.

--
Derk Gwen http://derkgwen.250free.com/html/index.html
I ASSURE YOU WE'RE OPEN!

[osmium]

Neil Zanella writes:

I am curious as to why the designers of C did not include support for
Pascal-like nested procedures. I guess that it's because nested procedures
in C would not buy you much other than marginally cleaner namespaces, and
then again C has a static keyword for limiting the scope of functions to
a file, which is not quite the same, but seems enough for all practical
purposes. Anyone care to either agree or disagree?

I see it (The C way) as the natural view of the world as seem by an assembly
language programmer.

[CBFalconer]

Keith Thompson wrote:

Neil Zanella <nz******@cs.mu n.ca> writes:

I am curious as to why the designers of C did not include support
for Pascal-like nested procedures. I guess that it's because
nested procedures in C would not buy you much other than
marginally cleaner namespaces, and then again C has a static
keyword for limiting the scope of functions to a file, which is
not quite the same, but seems enough for all practical purposes.
Anyone care to either agree or disagree?

I suspect part of the reason is that disallowing nested procedures
makes the compiler's job easier, something that was probably more
important when the language was being designed than it is now.

In Pascal, which was originally designed to have a single source
file and no separate compilation facilities, the feature was very
attractive for proper localization. In C, with the separate
compilations, it is much less necessary inasmuch as there are
other methods of limiting scope.

--
Chuck F (cb********@yah oo.com) (cb********@wor ldnet.att.net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home .att.net> USE worldnet address!