This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: <built-in> vs <internal>
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Per Bothner <per at bothner dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 28 Jun 2004 14:01:04 -0700
- Subject: Re: <built-in> vs <internal>
- References: <40E07FD1.6010701@bothner.com>
Per Bothner <per@bothner.com> writes:
> While initializing, some code (including cpplib) sets the
> current filename to "<built-in>" while other code (including
> c_init_decl_processing) uses "<internal>". What is the
> distinction? Any reason not to use "<built-in>" consistently?
I don't think there's any difference, just a change in preferred
terminology over time. I'd approve a patch that changed everything to
use "<built-in>" (or "<internal>", don't care which).
zw