[fpc-devel] Re: Debugger for FPC

[Jonas Maebe]

On 14 Mar 2009, at 09:16, dmitry boyarintsev wrote:

>> And in fact, the same can be done to generate for properties that  
>> directly
>> map to variables/fields. Just one question: what should the debug
>> information point the debugger to in case of
>> a) a property without a read specifier, but with a write specifier  
>> going
>> directly to a field? Nothing, or that field?
>> b) a property with a read specifier that is a function call, but  
>> with a
>> write specifier directly going to a field? Nothing, or that field?  
>> (as long
>> as we do not support encoding property accessor function calls into  
>> the
>> debug information, and/or when we do but determine that the  
>> accessor can
>> have side effects)
>
> how about:
> c) a property with a read specifier and write specifier?

I didn't mention that because if the read specifier is just a field,  
then the debug info should obviously simply point to that field (when  
you ask the debugger for the value of a property, I think you'd  
normally expect it to give you the value that you'd get when reading  
the property). And if it's a function, it's not yet possible to call  
it at this time.


Jonas