Namespace for inner classes in jextract

[Duncan Gittins]

On 11/03/2021 12:49, Maurizio Cimadamore wrote:
>
> On 11/03/2021 12:19, Maurizio Cimadamore wrote:
>>
>> There's some validation to do when it comes to duplicate names - for 
>> instance, struct names can clash with typedef names, etc. which 
>> probably suggests that the syntax of the option will have to be more 
>> convoluted. 
>
> There's also another issue with  --sym - which is that, as described, 
> I think you are assuming this semantics:
>
> * if no --sym is specified on the command line, do whatever jextract 
> does today
> * if one (or more) --sym is specified, then switch into a mode which 
> means "only these please!"
>
Yes - easily applied after --filter options are dealt with, much in the 
way that many SQL apps may optionally append "AND blah in ( ....)" to a 
query needs an extra filter:

         if (!symbols.isEmpty()) {
             toplevel = filterByName(toplevel, symbols);
         }

> I have a feeling that, maybe, we are trying to conflate too much in a 
> single option? That said I see the simplicity appeal.
>
> Maurizio
>
>
>