[GRASS-dev] GRASS and QGIS on Win32, testing etc.

Michael Barton michael.barton at asu.edu
Mon May 21 17:12:37 EDT 2007

Once the wxgrass GUI gets to a semi-complete state (pretty soon actually), I
thought it would be a good exercise to try rebuilding a script or two in
python to see how it goes. I have the impression that it will be a lot
easier and use much less code than bash shell scripting to do complex things
and about the same amount of code to do simple things. If anyone wants to
try, I will help test.


On 5/21/07 12:11 PM, "Glynn Clements" <glynn at gclements.plus.com> wrote:

> Moritz Lennert wrote:
>> This also means that any shell scripts (e.g. g.mremove, v.dissolve, etc)
>> will either have to be replaced by C-versions (which kind of defeats
>> their purpose of being easily codable for a larger number), be coded in
>> a cross-platform scripting language (e.g. Python), or anyone who wants
>> to use these under Windows has to provide access to a series of shell
>> tools (e.g. through Msys).
> Personally, I would favour switching to Python.
> Apart from the portability issues, both Bourne shell and C shell are
> *really* poor as general-purpose programming languages.
> If you just want to run a sequence of commands, then a shell saves you
> the trouble of having to quote the arguments and prefix the command
> with an "exec" (or similar) command, as would normally be the case for
> a normal programming language.
> As soon as you get beyond that, the fact that they were designed as
> interactive shells first and programming languages second starts to
> become a major problem.

Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton 

More information about the grass-dev mailing list