[GRASS-dev] script programming

Maris Nartiss maris.gis at gmail.com
Tue Jan 29 05:58:23 EST 2008


Hello,
sorry for asking, but I was not able to understand what kind of
information You need. Please be so kind and clarify it.

Currently GRASS does not use any FORTRAN code, still GRASS modules can
be written in any language of programmers choice (tough there's high
possibility, that non-C/TCL/Python modules will not be included in
main source tree). Tough there is an official GRASS ZOO for such code
- more info about GRASS AddOns can be found here:
http://grass.gdf-hannover.de/wiki/GRASS_AddOns

Compiling Fortran code is a bit offtopic here. GCC webpages could be
more helpfull. http://www.gnu.org/software/gcc/fortran/

The best way how to understand g.parser usage in scripts (for use in C
modules look in GRASS programmers manual) is to look on some recent
scripts in GRASS source tree. Look in to /scripts folder for examples.

WBR,
Maris.


2008/1/29, roberto marzocchi <roberto.marzocchi at gmail.com>:
> Hi,
> sorry, I've some basic questions about script programming in GRASS.
>
> I've created a GRASS-script to obtain flooding map for my  thesis, and now I
> want
> to make public knowledge this script.
> So, I see the grass general command  g.parser and I think to use it,
> but I've a problem with portability.
> I've created a lot of parts of my script in FORTRAN language, but I don't
> know
> if to compile fortran code is possible.
> It's possible? how?
> Other  suggestions?
>
> Thank in advanced
>
> Roberto M
>
>
> ******************************************************************************************************************************************************************************************************************
> Roberto Marzocchi
> for
> University of Genoa
> DICAT - DIMSET
>
> mail: roberto.marzocchi at gmail.com
> ******************************************************************************************************************************************************************************************************************
>


More information about the grass-dev mailing list