C / C++ / MFC

I hate blanket statements like that... Enums should be used for what they are meant for -- enumerations. That is, they should be used when you need to represent a set of values, but don't really care what the values are:

enum ACTION
{
   PRINT,
   PREVIEW,
   EXPORT
};

void DoOutput(const char* OutputDataString, ACTION action)
{
   switch (action)
   {
      case PRINT:
      ...
      break;
      case PREVIEW:
      ...
      break;
      case EXPORT:
      ...
      break;
   }
}

In the example above, it doesn't matter what the values of PRINT, PREVIEW, and EXPORT are, only that they are different. As the other post mentioned, the compiler will perform type checking on this to ensure that only valid values are passed into the function (of course you could use a cast, but you'd never do that right?).

In cases where the value of a constant is actually important, you should use a static const -- not only does this let you be consistent about your constants, since enums are only good for ints anyway, it is also safer, since if the value is important, sooner or later you'll need to convert it from something else, and assigning an int to an enum variable is (i think) undefined (though it usually works). If you need some extra type checking in this case, you're better off using a typedef or even a wrapper class.

3.6.1 Chunked Transfer Coding

   The chunked encoding modifies the body of a message in order to
   transfer it as a series of chunks, each with its own size indicator,
   followed by an OPTIONAL trailer containing entity-header fields. This
   allows dynamically produced content to be transferred along with the
   information necessary for the recipient to verify that it has
   received the full message.

       Chunked-Body   = *chunk
                        last-chunk
                        trailer
                        CRLF

       chunk          = chunk-size [ chunk-extension ] CRLF
                        chunk-data CRLF
       chunk-size     = 1*HEX
       last-chunk     = 1*("0") [ chunk-extension ] CRLF

       chunk-extension= *( ";" chunk-ext-name [ "=" chunk-ext-val ] )
       chunk-ext-name = token
       chunk-ext-val  = token | quoted-string
       chunk-data     = chunk-size(OCTET)
       trailer        = *(entity-header CRLF)

   The chunk-size field is a string of hex digits indicating the size of
   the chunk. The chunked encoding is ended by any chunk whose size is
   zero, followed by the trailer, which is terminated by an empty line.

   The trailer allows the sender to include additional HTTP header
   fields at the end of the message. The Trailer header field can be
   used to indicate which header fields are included in a trailer (see
   section 14.40).

-Masaaki Onishi-