[cfe-dev] RFC: Clang driver redesign (round 2)

[David Chisnall]

On 8 Nov 2011, at 12:10, Alek Paunov wrote:

> On 08.11.2011 13:23, James Molloy wrote:
>> Many people want to have a configuration file that can do almost
>> everything at invoke-time, but to cover all use cases that would
>> require turing completeness and a full-on scripting language, which
>> has been pooh-poohed already (and I don't agree with anyway).
> 
> The two can be combined I think - configuration for let say 90% of the 
> cases + scripting language loaded as optional plugin for the rest.
> 
> Regarding configurations flexibility: Usually there are antagonism 
> between the two polar structures of configuration trees: a) Structure 
> symmetrical to full internal representations (fast and simple 
> validation/loading/storing), z) Short, human-friendly DSL (possibly with 
> inheritances, aliases, etc). In many projects the problem is resolved 
> using additional tool which translates z) to a) on demand (only on z 
> change), using a) templates as base.

I wondered if some of the tablegen infrastructure couldn't be reused for this, so we could have a configuration file format that could be compiled into C++ for the common cases, avoiding the need to parse it on every invocation.

David

-- Sent from my PDP-11