2017-04-30 08:53:34 UTC
when range checks are on (-Cr):
An explicit check for nil is generated, which seems redundant, as any
attempt to use the value will generate a SIGSEGV anyway on most
platforms, or am I missing something?
If the fpc_check_object fails it calls RunError, which forces the
application to terminate, whereas a SIGSEGV will raise an exception and
give the user the option of continuing (at least in an LCL app). Is
there any reason why fpc_check_object does not call HandleError?
fpc-devel maillist - firstname.lastname@example.org