🚀 go-pugleaf

>>>>> "BK" == Bob Kline <bkline@cortex.nlm.nih.gov> writes:
[...]
BK> Here's the other case:

BK> template<size_t N> bitset<N> operator&(const bitset<N>& lhs, const
BK> bitset<N>& rhs) { return bitset<N>(lhs) &= rhs; }

BK> To which the compiler responds:

BK> "./bitset", line 333: Error: The template argument N is not a
BK> type.

BK> Why is this?  The same compiler accepts the "template<size_t N>
BK> class bitset { ... }" quoted above, so I'm puzzled.  However, this
BK> isn't the only compiler which accepts the first use of a non-type
BK> template argument and rejects the second, so I'm beginning to
BK> suspect I'm just missing something obvious.  Can someone point it
BK> out to me, please?

Until not so long ago, non-type template parameters were prohibited
for function templates (e.g., see ARM 14.4). Many compilers still
impose that limitation.

	Daveed



[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]