Am 26.12.2017 13:33 schrieb "Giuliano Colla" <giuliano.co...@fastwebnet.it>:
If the idea is not rejected, then a number of refinements (which I'm ready
to implement) are required to make the feature generally available:
My following remarks are independent of an eventual acceptance of the
feature :
- All architectures should be supported (now it's only for x86_64 -
symcpu.pas).
It might be possible to implement this in a platform independent way that
might simply need to expand the capabilites of "absolute".
- It should be decided if to make the feature generally available, or
conditioned by an {$IFDEF FPCHASBASED}
- It should be decided if the feature should be available in all modes or
only in a selected number of modes (what of TurboPascal Mode or Delphi
Mode?).
Rule of thumb: new features added as a separate mode switch, no FPC_HAS_*
define necessary as by definition this can be done with version checks
(there is only one trunk version, namely the current one).
- It should be decided if error messages should be specific for the BASED
construct or common to the ABSOLUTE one, slightly rephrasing the error
message.
Might be one or the other depending on the message.
- It should be decided if internal error # which currently keep the same
number of the nearby ABSOLUTE internal error should be given new values.
Internal errors shall always be unique as they are used to find the error
location, even for copy pasted code.
Regards,
Sven
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
