On Mon, Feb 8, 2010 at 11:03 PM, Glynn Clements <gl...@gclements.plus.com> wrote: > Actually, I would suggest QGIS/vdigit isolating actions within a child > process, rather than complicating the rest of GRASS for the sake of > two programs, one of which isn't part of GRASS and the other was > designed incorrectly from the outset.
That would mean tho have a communication infrastructure (protocol,library) for sending data between either digit tool and main application or between main application and some sort of digit server. And that is a lot of work. More than to support returning error codes in vector lib where necessary IMO. So well, less work in GRASS much more work for QGIS, vdigit, GDAL and via GDAL Mapserver, R or other applications. Consider also that those applications are written and working so changing them completely is huge amount of work. I understand your point of view but I don't agree with. All this started with -fexception which can solve the problem (on cost of some memory leaks). I think that the easiest solution fo QGIS and GDAL is to create a new project "Exceptional GRASS" as a copy of GRASS core libs with Lib.make patched to compile with -fexception. There was once libgrass already, IIRC, the support for fatal error handler was introduced there for R. Radim _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
