Complete.Org: Mailing Lists: Archives: freeciv-dev: September 2000:
[Freeciv-Dev] Re: [PATCH] Names in rulesets. (PR#559)
Home

[Freeciv-Dev] Re: [PATCH] Names in rulesets. (PR#559)

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Erik Sigra <freeciv@xxxxxxx>
Cc: freeciv-dev@xxxxxxxxxxx, bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: [PATCH] Names in rulesets. (PR#559)
From: Gaute B Strokkenes <gs234@xxxxxxxxx>
Date: 16 Sep 2000 16:34:43 +0200

Erik Sigra <freeciv@xxxxxxx> writes:

> Gaute B Strokkenes wrote:
> 
> > I think a fatal error is a bit harsh, though.  And I think we
> > ought to allow case variations.
> 
> I don't think it is too harsh considering it can be easily fixed by
> the ruleset creator.

So she fixes the error, and then five minutes later, when she gets
around to running civserver again, civserver dies with another error.
Repeat ad nauseum.  I think it's much easier on the creator to go on
loading the rules and list as many errors as possible before
(possibly) dying.  This is why gcc and friends don't die when they
encounter the first error in file.  It would be a real pain to use
them if they did.  (Off course civserver isn't gcc, but...)

> In princlple I like things that force correctness.

Really?  Did you ever hear about "bondage and discipline" languages?

In principle, I think that software should be robust and not die when
faced with errors that it can easily recover from.

> What would case variations be good for?

Why not?  So that you can write "male" instead of "Male", for
instance.  There are a number of places where case sensitivity _is_
appropriate, mostly because it would confuse gettext(), but I don't
think this is one of them.

-- 
Big Gaute (not to be confused with LG)
Yow!  I'm imagining a surfer van filled with soy sauce!



[Prev in Thread] Current Thread [Next in Thread]