Re: [PATCH] Use variants to support objects as semantic values.

[Akim Demaille]

Le 22 oct. 08 à 01:00, Akim Demaille a écrit :

> This patch was inspired by work by Michiel De Wilde.  But he used  
> Boost
> variants which (i) requires Boost on the user side, (ii) is slow, and
> (iii) has useless overhead (the parser knows the type of the  
> semantic value
> there is no reason to duplicate this information as Boost.Variants  
> do).

I know that this patch is not fully functional, it has problems with  
the lookahead not being always properly destroyed.  But it was already  
complex enough this way, and I did not manage to rebase in such a way  
that I could easily fuse with the fix that follows.  Besides, it does  
not work when variants are used, but the skeleton in default mode  
still works properly.

I used "%define variants" for lack of a more intelligent name.  Joel,  
you might have an opinion about this.  Maybe api.type.variants?

I just say that the java skeleton now uses %define stype, which is  
correlated.  I regret that the names were not discussed first, now we  
face a lack of structure, although Joel had been careful up to now to  
propose something consistent.

If the Java people can come with better names, more structured, that  
would be nice.

We need to write a guideline for these directive names.