Re: [boost] BOOST_PP_ENUM_PARAMS can't be nested inside BOOST_PP_IF?

From: Tobias Schwinger (tschwinger_at_[hidden])
Date: 2006-01-29 11:13:39

Paul Mensonides wrote:
>>-----Original Message-----
>>From: boost-bounces_at_[hidden] 
>>[mailto:boost-bounces_at_[hidden]] On Behalf Of Tobias Schwinger
> 
> 
>>>>Note: 
>>>>- BOOST_PP_IF does not get disabled
>>>
>>>IF getting disabled doesn't matter here.  The entire ENUM_PARAMS 
>>>invocation occurs on entry to IF--where IF is not get disabled.
>>
>>Right, otherwise "BOOST_PP_CAT(f,BOOST_PP_CAT(o,o))" wouldn't work...
>>
>>  #define BOOST_PP_LOCAL_MACRO(i) I must not post rubbish when in a hurry. 
>>  // ... ;-)
>>
>>
>>Thanks for correcting,
> 
> 
> Not rubbish.  Your solution was the correct one--move the invocation of
> ENUM_PARAMS out of the input to IF.  
> 

Oh - I don't think my whole post was rubbish, but that note sure was (and due to quick-posting). I'll cite myself on the very same topic some weeks ago:

  Rescanning happens /after/ argument substitution [ 16.3.4.-1 ] and the replacement 
  restrictions for rescanning [ 16.3.4-2 ] do not apply for argument substitution [ 
  16.3.1 "A parameter in the replacement list [...] is replaced by the corresponding 
  argument after /all/ macros contained therein have been expanded" ].

Hmmm...

> [... Chaos] 

I hope to understand more after reading your reply to my Chaos questions (no need to hurry).

BTW. should I better ask somewhere publicly (the seemingly dormant Sourceforge forum of the chaos-pp project, perhabs) rather than in private email? 

Regards,

Tobias