Re: [long][code][problem][compile][unix][newbie][attachment][error] Compileing errors

From: Daniel Koepke (dkoepke@california.com)
Date: 01/17/97


Use a god damn subject instead of all those fucking bracketed flags.
It makes more sense.  Eg.,

  "Compiling Errors"

instead of:

  "[long][code][problem][compile][unix][newbie][attachment][error]
   Compileing errors"

First off, you don't need to specify "long", since your message wasn't
long.  You don't need to provide "problem" and "error" since they imply
one another, and you don't need to provide either since both are
covered in your actual subject.  Same goes for "compile", and, again
for the "[unix]" flag, since very rarely is there problems with code
that exist only upon UNIX platforms and none other.  Attachment is not
necessary, since they can tell if it has an attachment or not by
looking at the message.  That has us down to:

  "[code][newbie] Compileing errors"

If you're having compilation errors, that implies it has to do with
code, and usually people provide faulty code.  You can leave newbie,
and fix the spelling error.  Ta'da.  It's actually readable and
acceptable.


--
Daniel Koepke
dkoepke@california.com
Forgive me father, for I am sin.


+-----------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
|   http://cspo.queensu.ca/~fletcher/Circle/list_faq.html   |
+-----------------------------------------------------------+



This archive was generated by hypermail 2b30 : 12/18/00 PST