Complete.Org: Mailing Lists: Archives: freeciv-dev: November 2001:
[Freeciv-Dev] Re: commandline syntax and semantics (was: Server/ruleset

[Freeciv-Dev] Re: commandline syntax and semantics (was: Server/ruleset

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Reinier Post <rp@xxxxxxxxxx>
Cc: Freeciv developers <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: commandline syntax and semantics (was: Server/ruleset unification)
From: Daniel Sjölie <deepone@xxxxxxxxxx>
Date: Sun, 4 Nov 2001 17:11:59 +0100

On 2001-11-04 09:41:45, Reinier Post wrote:
> On Sun, Nov 04, 2001 at 01:44:56AM +0100, Daniel Sjölie wrote:
> > Actually, now that I think about it... How hard would it be to actually
> > use a subset of (or very heavily inspired by) sql syntax? That would solve
> > our problems nicely I think... I've kind of written that of earlier because
> > it might be overly complex but maybe it really wouldn't be that hard...
> > It certainly would have a lot of advantages, right?
> The easiest way to support that is to make civserver use a database.
> It's nice to have generic selections, but I would only use SQL syntax if
> there is actually a relational database underneath, which has advantages
> in itself.
> > The convenient syntax above should be specific for the command line
> > server (no need for this in a gui-server) and _implemented_ _using_ the
> > "ruleset-language"... So that /ai Napoleon could become:
> > 
> > update players set ai=not ai where name="Napoleon"
> > 
> > Server commands should not be part of the language but there should be a
> > server command that would take a "ruleset-language" statement as
> > argument and execute it...
> > 
> > This would give the best of all worlds, wouldn't it?
> > Do you think it's too much?
> I prefer to have as few languages as possible.  Your HSQL (Homegrown SQL)
> won't be SQL so it's best not to make it seem like SQL.

Are you saying that this is all a bad idea or that we should use a
"real" database instead?

I don't agree either way... :)

I don't a real database can be used in a good way and I don't really
see the problem with a new language heavily inspired by sql... We don't
need all of sql but I think being hevily inspired by the parts that solve
the problems interesting for us here is a good thing...

I see no point in creating a language with no similarities with any
other language just to avoid confusion... I think most that know sql
would prefer a sql-like language to something totally new and it
shouldn't matter to those who don't know sql...


Now take a deep breath, smile and don't take life so seriously... :)

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