🚀 go-pugleaf

In article <1991Apr26.155106.10943@sparky.IMD.Sterling.COM> kent@sparky.IMD.Sterling.COM (Kent Landfield) writes:

   This is being done with the Environment: header line in comp.sources.games.

When we were discussing how to do things in c.s.r, we discussed
putting the environment information in a header line.  However, we
decided in the end not to do this for a few reasons (and I'm sure that
if I forget any of them, someone else who was involved in the
discussion will pipe up):

1. Non-standard header lines are, in general, a bad idea.  For
   example, the header lines that rn is capable of manipulating (i.e.
   showing vs. hiding) are hard-coded, and it can't deal with any
   lines that aren't in its hard-coded list (obviously, this is a
   major lose, and some newsreaders {such as xrn} have overcome this
   difficulty, but it's still a problem).

2. The environment information often takes more than one line.  Or, in
   order to fit it on one line confusing abbreviations sometimes have
   to be used.

3. Archives are often kept of shar files without saving the headers of
   the messages that came with the shars.  If important information is
   in the header, that information ca be lost.

So, the end result of our discussion was the conclusion that the
environment restrictions on packages would be described in the text of
its introductory posting, rather than in a header line.

Of course, if comp.sources.games has been using a header line, and
they haven't had any problems, perhaps we should reconsider our
decision.  But I think I'll hold off on suggesting that until we do it
the way we've decided to for a while so that we have something we can
compare against how comp.sources.games does things.

Jonathan Kamens			              USnail:
MIT Project Athena				11 Ashford Terrace
jik@Athena.MIT.EDU				Allston, MA  02134
Office: 617-253-8085			      Home: 617-782-0710