[fpc-devel] Object checks

[Pierre Muller]

Hi Colin,

Le 30/04/2017 à 10:53, C Western a écrit :
> If I may, a couple of queries about code generated for object checking 
> 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?

  Thanks for the suggestion,

  I applied a patch in commit 36113 to trunk that
substitutes RunError with HandleError.
It has been applied to three functions:
fpc_help_destructor, fpc_check_object and fpc_check_object_ext



Pierre