This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Target-specific Front-Ends? (Was: front end changes for altivec)
At 12:10 PM -0800 11/27/01, Geoff Keating wrote:
>Ira Ruben <ira@apple.com> writes:
>
>> At 8:47 AM -0600 11/27/01, Aldy Hernandez wrote:
>>
>> > couldn't tolerate "vector" being a macro that expanded to __vector
>> >
>> >uhhh, that's exactly what i'm going to do for gcc. it's either that or
>> >keep a separate set of patches.
>>
>> And if someone is trying to use stl's class vector then what happens?
>
>It won't work. There's little or nothing that can be done about that;
>it wouldn't work even if 'vector' was a keyword.
That was a rhetorical question!
It was precisely that reason why 'vector' was made a context
sensitive type id and not a unconditional keyword. Doing it that way
allowed it to be used in that type context while still allowing class
vector to work or the use of 'vector' in any other way.
Ira