C++ and GRASS (was: [GRASS5] Want GNU libavl ?)

[Bernhard Reiter]

> Frank Warmerdam wrote:
> > David D Gray wrote:
> > > We could talk about this for ever, but it can only be put to the test
> > > when a developer comes up with a specific proposal with genuine merit
> > > for  including or writing a component in C++ (or other language).

> > I hardly want to be a proponent of "C++ ification" of GRASS; however, I
> > would like to see the GRASS build system attempt to identify a C++ compiler
> > that can be used (normally just g++ of course) and to support building C++
> > modules.

To identify a c++ compiler is fine in the build system is fine.

> > For the time being I think we should avoid using C++ in libraries but I
> > think we should open up the option of some programs being in C++.

This is reasonable as long as we point people to the problems of C++.
GRASS is Free Software we will not stop people from using it from C++.

> > Therefore, I propose that for GRASS 5.1 we open up the option of some
> > GRASS programs (hopefully non-essential ones) be written in C++.  

We should make it a requirement that they are non-essential.

> > Hopefully
> > from this we will get a better sense of what portability problems we will
> > encounter with C++.  Then in GRASS 5.2 we can consider allowing some C++
> > code in the core libraries.

Sounds like a plan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 248 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20020124/c203162d/attachment.bin