On Tue, 2003-11-04 at 11:24, Richard Peters wrote: > Throwing an exception here does not make much sense, the > CRYPTO_COMPILE_ASSERT is there to assert the condition _at compile time_, > throwing an exception delays the error until runtime. > The unused code warning is probably generated by the way the compiletime > assert is made, but that doesn't mean that it can be removed. > > Richard Peters
It seems a bit odd to do this at compile time. That is just my simple understanding of the code so far. It says that you are accepting in a const class T type by reference. You then make sure that the lenght of it is only one character like an array. It does not seem like you want a single character from the function signature. It looks like a string is possible with 1+ characters. I would think it would be better to say: template <class T> ConstByteArrayParameter (const T &char, bool deepCopy = false) With this I know that you are expecting in only a single character. In the end I don't know where this function would be useful. An example would be nice to see. Stephen -- Stephen Torri GPG Key: http://www.cs.wustl.edu/~storri/storri.asc
signature.asc
Description: This is a digitally signed message part
