[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] null bindings
|
As a minimum, some of the preprocessor nodes (e.g. the name of an
include statement) do not resolve to any binding, they return null.
Markus.
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mike Kucera
> Sent: Thursday, April 03, 2008 10:38 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] null bindings
> Importance: Low
>
>
> Question for the experts....
>
> When exactly does IASTName.resloveBinding() return null? From
> what I can tell it returns a ProblemBinding for all names
> that can't be resolved, and only returns null for empty name
> nodes, that is dummy name nodes created by the parser that
> don't actually correspond to an identifier in the source.
> Is this correct?
>
> I'm asking because I've been experimenting with adding a new
> type of ambiguity node, an ambiguous declarator. The
> ambiguity resolution code in CPPASTAmbiguity counts both
> ProblemBindings and null bindings as problems.
> But it seems to me that null bindings aren't really problems
> if they are just the result of dummy name nodes, and
> therefore shouldn't be counted. Am I missing something here?
>
> Thanks.
>
>
> Mike Kucera
> Software Developer
> IBM CDT Team, Toronto
> mkucera@xxxxxxxxxx
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
