On Wed, Jun 19, 2013 at 1:56 PM, Nelson, Clark <email@example.com> wrote:That is probably practical for <cstddef>, but less so for <stddef.h>,
>> I objected that I did not want including <cstddef> to require the
>> implementation to perform header search for <optional> and
>> (and whatever other headers we add in the future). I would expect
>> issuing these file system requests to have a measurable cost.
> OK. And you don't think it's practical for <cstddef> just to know the right answer, and unconditionally define either or both of those two macros as appropriate?
which is frequently provided by the compiler implementer rather than
by the C++ standard library implementer. If we're happy for <stddef.h>
to not provide these macros, then the suggestion of putting them in
<cstddef> seems fine to me.