Complete.Org: Mailing Lists: Archives: freeciv-dev: October 2001:
[Freeciv-Dev] Re: Split patch (was Re: [RFC PATCH] init_techs)
Home

[Freeciv-Dev] Re: Split patch (was Re: [RFC PATCH] init_techs)

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Daniel L Speyer <dspeyer@xxxxxxxxxxx>
Cc: "Ross W. Wetmore" <rwetmore@xxxxxxxxxxxx>, Freeciv developers <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: Split patch (was Re: [RFC PATCH] init_techs)
From: Reinier Post <rp@xxxxxxxxxx>
Date: Mon, 1 Oct 2001 16:12:32 +0200

On Mon, Oct 01, 2001 at 08:28:44AM -0400, Daniel L Speyer wrote:
> On Mon, 1 Oct 2001, Reinier Post wrote:
> 
> > On Sun, Sep 30, 2001 at 07:51:10PM -0400, Ross W. Wetmore wrote:
> > > But I think it has been said many times that such flexibility is not
> > > required for Freeciv. It would be a wise move to really look at the
> > > pros and cons before introducing such parse elements into any future 
> > > command syntax design.
> > 
> > I agree, neither the ; or the ability to let commands continue on the
> > next line seem required.  It's just nice to have.
> 
> It seems to me that the cases in which this could be very nice are those
> which are concetually multiline anyways (such as oject
> initialization).  How about allowing braces, which combine several
> commands into an argument?  So, for example:
> 
> create tech.hacking { #Needed for internet
>   set req1 computers; set req2 theology
>   set name "Hacking"
> }
> 
> Would create a namespace tech.hacking and then use it as a root namespace
> for the following commands.  (The simplest parsing routine would probably
> make there be four commands, the first of them of length zero.  This
> command should simply do nothing.)

This is nice and powerful, but if it was up to me, I would prefer to
restrict . notation to match the actual Freeciv datastructures.
 
> --Daniel Speyer
> "May the /src be with you, always"

-- 
Reinier


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