Boost logo

Boost :

From: Felipe Magno de Almeida (felipe.m.almeida_at_[hidden])
Date: 2007-05-20 23:30:15

On 5/20/07, Hartmut Kaiser <hartmut.kaiser_at_[hidden]> wrote:
> Felipe,

> [snip]

> Ok.
> - Introspecion of defined include paths is currently not available. I'll
> think of a possible interface.


> - I don't know what you want to get from introspecting #pragma's. There is
> no data structure in Wave collecting information about these. But what you
> can do is to implement the 'interpret_pragma' preporcessing hook, which
> get's called whenever a #pragma directive has been detected in the input
> stream not known to the core Wave library itself (you may want to have a
> look at the wave driver tool to see how it works).

I've seen it. I'm not sure if pgrama's are really that important. It
is just that it may be part of the preprocessor state.

> - Macro management is fully implemented as long as you know the name of the
> macro to analyse. The context object has several functions useful for that:
> add_macro_definition(), is_defined_macro(), get_macro_definition(),
> remove_macro_definition() and reset_macro_definitions(). What's missing here
> is a function returning all defined macros - is this something you might
> want to have?

That's exactly what I want. I want to know which macros are defined in
some "random" point of the preprocessing. For that I need iterators
for all macro definitions.

> Regards Hartmut

Best regards,

Felipe Magno de Almeida

Boost list run by bdawes at, gregod at, cpdaniel at, john at