deadpickle wrote:
Thanks for the replies. Just as a note, the warnings are caused by the
variable being a const. Omitting the const solved it.
I'm not sure if this is a C program or a GDAL thing, thats why I'm not
sure where to post this at, but I get a segfault. I know segfaults are
generally ca
I accedently replied off list so I will send it again with a couple of
additions.
deadpickle
One of c's drawbacks is its not safe unless you do it right, pointers
are very good at letting you access memory you don't own. To hunt down
such problems you can run your app under the valgrind utility o
Thanks for the replies. Just as a note, the warnings are caused by the
variable being a const. Omitting the const solved it.
I'm not sure if this is a C program or a GDAL thing, thats why I'm not
sure where to post this at, but I get a segfault. I know segfaults are
generally caused by ordinary, an
You need to buy a book about C/C++ or ask on comp.lang.c or comp.lang.c++
Best regards,
-
--
Mateusz Loskot
http://mateusz.loskot.net
--
View this message in context:
http://n2.nabble.com/gdal-dev-C-GDAL-beginner-tp4665330p4666854.html
Sent from the GDAL - Dev mailing list archive at Nabb
Thanks for the reply. I was wonder what the deal is with the other
warnings:
#include "ogr_api.h"
#include "ogr_srs_api.h"
int main()
{
//~ variable declaration
const char *format = "ESRI Shapefile", *name = "testc.shp", *source,
*target;
const char *sprj = "+proj=lcc +lat
