|
|
Boost : |
From: Eric Friedman (ebf_at_[hidden])
Date: 2002-07-25 18:22:21
Mat Marcus wrote:
[snip]
> Hmmm. For me, metafunction type doesn't capture the role played by this
construct for the user.
> And it still seems like it can be misread as "type of the metafunction".
Other ideas: "metafunction
> object" or "metafunction value"?
What about "delayed metafunction"? The desire to _delay_ the application of
a metafunction is the
reason this metafunction/metafunction-class distinction was created in the
first place. (No?)
"Delay" also has precedent in the Boost Preprocessor library (for similar
reasons).
Just another 2 cents,
Eric
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk