🚀 go-pugleaf

Paul Eggert <eggert@twinsun.com> wrote:
>But suppose there turns out to be a problem with __FUNCTION__ and the
>existing phases-of-translation model.  Since __FUNCTION__ is the most
>useful design, if the phases-of-translation model prohibits it then we
>should fix the phases-of-translation model.  We shouldn't adopt a less
>useful design simply because our theory is inadequate.  And fixing the
>model would be relatively easy.

Of course, the supposed "separate" translation phases *already* cannot
be implemented separately.  The result of __LINE__ is dependent on the
state of the translation unit as it is between stages 1 and 2, i.e. a
full two stages before preprocessing, so no tokenisation has happened
yet.  There's no serious problem with handling __FUNC__ or __FUNCTION__
in the compiler.  It's awkward to see what would happen to string
concatenation with __FUNCTION__ in terms of the current model, but that
should not preclude the possibility of using this feature.

-zefram