I would propose adding non-fatal error reporting function to gislib.
New G_error() would act in the similar way as G_fatal_error() except
of calling exit(). Currently if you want to report error message
without calling exit() you need to use G_warning() instead.
I would propose adding non-fatal error reporting function
to gislib.
New G_error() would act in the similar way as G_fatal_error()
except of calling exit(). Currently if you want to report error
message without calling exit() you need to use G_warning()
instead.
Hi,
can you provide an example of for when it would be useful?
under what conditions is an error non-fatal?
i.e. when would it be preferable over simply using
G_important_message("ERROR: ...") ?
I would propose adding non-fatal error reporting function to gislib.
New G_error() would act in the similar way as G_fatal_error() except
of calling exit(). Currently if you want to report error message
without calling exit() you need to use G_warning() instead.
If the issue doesn't prevent the program from operating, is it really
an error?
Or is this intended for the case where you want to separate reporting
from termination?