[boost] [local_function] End scope function name declaration makes code hard to read.

Subject: [boost] [local_function] End scope function name declaration makes code hard to read.
From: Mostafa (mostafa_working_away_at_[hidden])
Date: 2013-03-15 17:33:29

(This is a feature request/inquiry.)

I'm just now seriously starting to use local_function, and I'm finding  
that having to "visually parse" until the end of scope to determine the  
local function name makes the code much harder to read. Is it possible to  
declare the function name at the beginning of the scope? (I don't mind  
having to also register the function name at the end of the scope.)  
Something like:

BLF2(add, (int), (int lhs, int rhs))
{
     return lhs + rhs;
} BLF2_REGISTER(add);

Having said, I don't see why needing an "ending macro" for the local  
function scope is a requirement (albeit my understanding of the library  
internals is limited to implementation annex of the documentation). Can't  
the start macro just expand to something like:

//-----------------------------
//Macro Generated Output Start.
//-----------------------------
//Local class definition.
//Local class instance registration.
//Out of class method definition starts here:
inline void local_add::body(int& sum, const int& factor, const int& num)
//-----------------------------
//Macro Generated Output End.
//-----------------------------

//User generated content starts here:
{
     return lhs + rhs;
}

Thanks,

Mostafa