Self-inlining anonymous closures in C++

http://matt.might.net/articles/static-closures-in-c-plus-plus/

by adg001 • 16 years ago

52 8 16 years ago

matt.might.net

omnigoat• 16 years ago

Sorry, I can't see how this is an improvement over Boost::Phoenix:

http://www.boost.org/doc/libs/1_44_0/libs/spirit/phoenix/doc...

util• 16 years ago

Thanks for the pointer!

jrockway• 16 years ago

Now you get to run yourself in Valgrind to see if your guess about who's supposed to free it is correct.

mattmight• 16 years ago

It isn't meant to be an improvement or a replacement.

It's just a tutorial on how such things are done. :)

jongraehl• 16 years ago

$ in C++ identifiers is a nonstandard extension that gcc allows on some platforms - cool (and not portable).

gjm11• 16 years ago

You could use, say, "ARG_" instead and it would work just the same. (Phoenix uses "arg".)

shin_lao• 16 years ago

A lot of people will read this and think "damn C++ is such an ugly language, it should never allow the programmer to do this!".

The reality is that that kind of technique allows to produce extremely fast code because the compiler has got so much "certain" information at compile time that it can optimize very aggressively.

It's more powerful than vanilla C macros because it works with the compiler, not the pre-processor.

andymorris• 16 years ago

C++ is the highest-level language that I can accurately guess the assembly that will be actually run by the processor.

YMMV whether that's a blessing or a curse, though!

Self-inlining anonymous closures in C++

Related Stories