Re: FAQ 1.12--auto keyword



"Bill Pursell" <bill.pursell@xxxxxxxxx> wrote:

The faq (question 1.12) states that the keyword "auto" is completely
useless.
However, it is necessary to forward declare a nested function (for
gcc...I'm not sure if this is gcc specific or a language issue.)

There is no such thing as a nested function in ISO C.

If gcc allows nested functions, that's its business. However, if it
requires "auto" to forwardly declare them, this is broken. They should
have chosen "static".

Richard
.



Relevant Pages

  • Re: FAQ 1.12--auto keyword
    ... it is necessary to forward declare a nested function (for ... It's gcc specific. ... Nested functions are not part of the language proper. ...
    (comp.lang.c)
  • Re: FAQ 1.12--auto keyword
    ... it is necessary to forward declare a nested function (for ... gcc...I'm not sure if this is gcc specific or a language issue.) ... Standard C doesn't allow nested function definitions. ...
    (comp.lang.c)
  • Re: FAQ 1.12--auto keyword
    ... it is necessary to forward declare a nested function (for ... that was existant but previously useless. ... to invent a new one. ...
    (comp.lang.c)
  • Re: FAQ 1.12--auto keyword
    ... it is necessary to forward declare a nested function (for ... If gcc allows nested functions, ...
    (comp.lang.c)
  • Re: FAQ 1.12--auto keyword
    ... There is no such thing as a nested function in ISO C. ... If gcc allows nested functions, ... requires "auto" to forwardly declare them, ... it gives you the ability to have functions that are visible only ...
    (comp.lang.c)