🚀 go-pugleaf

A couple of questions about situations in which I'm not sure why
the compiler (Sun's CC in this case) is rejecting some template code.
The first case involves the following code:

template<size_t N> class bitset { ... };
bitset<6> bs;

The compiler complains:
   Error: Template parameter N requires an expression of type unsigned. 

Two questions about this one: is this correct-- does the draft really
not allow an implicit conversion of the template argument here?  And
if it is correct, would it not be prudent to amend the bitset<N> 
class in the draft standard library to take an int instead of a
size_t template argument?  Template syntax is ugly enough already! 
:->}

Here's the other case:

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

To which the compiler responds:

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

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

--
/*----------------------------------------------------------------------*/
/* Bob Kline                                       Stream International */
/* bob_kline@stream.com               formerly Corporate Software, Inc. */
/* voice: (703) 522-0820 x-311                      fax: (703) 522-5407 */
/*----------------------------------------------------------------------*/

[ 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. ]