Complete.Org: Mailing Lists: Archives: freeciv-dev: September 2001:
[Freeciv-Dev] Re: Server/ruleset unification [Was [RFC PATCH] init_techs
Home

[Freeciv-Dev] Re: Server/ruleset unification [Was [RFC PATCH] init_techs

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Arien Malec <arien_malec@xxxxxxxxx>
Cc: Freeciv developers <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: Server/ruleset unification [Was [RFC PATCH] init_techs]
From: Raimar Falke <hawk@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 25 Sep 2001 21:18:05 +0200
Reply-to: rf13@xxxxxxxxxxxxxxxxxxxxxx

On Tue, Sep 25, 2001 at 11:55:08AM -0700, Arien Malec wrote:
> 
> --- Raimar Falke <hawk@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > > 1) The normal way to terminate a command is with '\n', but a create or
> > object
> > > set command is terminated with ';\n', since those sorts of commands are
> > likely
> > > to span lines
> > 
> > This is bad since the seperation f the commands into the two groups
> > isn't obvious to the user.
> 
> Alternatives are:
> 
> 1) Require that all commands be ';\n' terminated (which is an annoyance for
> most commands)
> 2) Require that an object create or set be newline terminated (which makes it
> hard to read
> 3) Have different termination rules for the server command line & rulesets
> 4) Disallow the (IMHO) convenient multi-attribute setting in create & object
> set

I would vote for 1). It is just one extra keystroke.

> Mostly the object create will be done in rulesets & the object set will be 
> done
> on command line (overrides of ruleset stuff), perhaps a reasonable solution is
> to make the 'create' command be the only oddball.
> 
> > > 2) Many of the commands either take a simple attribute or an object spec.
> > An
> > > object spec can always be distingushed by the presence of the reserved 
> > > word
> > > 'object'.
> > 
> > Bad since "object" is redundant.
> 
> For now, 'object' is redundant. The mention of 'tech' or 'player' will suffice
> to distinguish an object set from an attribute set. BUT (and the reason I
> introduced the keyword) that means that if we introduce a new object, it can't
> be the same name as an existing attribute. On reflection, that might be fine.

Can you show some examples of simple_set_statement and
object_set_statement. IMHO should these two be unified. So

 set players Caesar ailevel hard; OR
 set players.Caesar.ailevel=hard;

should be use the same syntax as a

 set unit archer vison 2; OR
 set unit.archer.vision=2;

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
 "USENET is *not* the non-clickable part of WWW!"


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