[fpc-devel] Re: Debugger for FPC
skalogryz.lists at gmail.com
Sat Mar 14 09:16:02 CET 2009
> 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)
c) a property with a read specifier and write specifier?
writing a property directly in the field is a hack, writing property
using setting procedure is correct way, with excpected "side-effects".
More information about the fpc-devel