OK.
On Tue, Oct 9, 2018 at 1:49 PM Paolo Carlini <paolo.carl...@oracle.com> wrote:
>
> Hi,
>
> On 09/10/18 17:17, Jason Merrill wrote:
> > On Sat, Sep 29, 2018 at 3:27 PM Paolo Carlini <paolo.carl...@oracle.com>
> > wrote:
> >> Hi again,
> >>
> >> On 9/28/18 9:15 PM, Paolo Carlini wrote:
> >>> Thanks. About the location, you are certainly right, but doesn't seem
> >>> trivial. Something we can do *now* is using
> >>> declspecs->locations[ds_typedef] and declspecs->locations[ds_alias],
> >>> but that gives us the location of the keyword 'typedef' and 'using',
> >>> respectively, whereas I think that we would like to have the location
> >>> of 'auto' itself. I could look into that as a follow-up piece work
> >> In fact, completing the work turned out to be easy: ensure that
> >> cp_parser_alias_declaration saves the location of the defining-type-id
> >> too and then consistently use locations[ds_type_spec] in the error
> >> messages. Tested x86_64-linux. Still Ok? ;)
> > Hmm, I think you need to look past any cv-qualifiers at the beginning
> > of the type-id.
>
> Ah, good point. The information is readily available in
> cp_parser_type_id thus we can simply return it to
> cp_parser_alias_declaration. I guess an alternate approach would be
> adding a pointer to the whole cp_decl_specifier_seq parameter to
> cp_parser_type_id (and cp_parser_type_id_1, etc), but that seems over
> killing to me.
>
> Thanks! Paolo.
>
> /////////////////////
>
