I'll investigate on changes and I'll come back later on
there is a checked inst var in PRCommand. I think I could use
similarly an inst var, or a wrapper for timestamp to associated it
with a boolean...
What would you do ?
I don't understand. There is already a time-stamp recorded within all
the commands (see inst-var refs to 'timestamp' in PRCommand). checked
is something else (see inst-var refs to 'checked' in PRCommand).
As any Magritte or Pier object you can just use #propertyAt: and
#propertyAt:put: and a Magritte description for clean extension
without having to override or change something in the existing code.
checked seems to be use only in PBComment...
"Answer ==true== if the command should be checked before
execution, e.g. the method ==#doValidate== should be executed at all."
This is used in PRPersistency. This is an important part of the
persistency mechanism and allows to replay commands at a later point
in time without checking the validation conditions. I agree, that the
implementation should be improved for readability.