In that case, if the functionality is going to be included, the best course of action might be to restore pre 2.4.0 behaviour, add the ability to use explicit dereference, and bind it to a separate mode switch.
Binding it to a mode switch solves the Delphi compatibility reason for removing it. Allowing both explicit and implicit dereference solves the consistency reason for removing it. And as Sven said, allowing absolute with expressions would be preferable to introducing a new keyword. > -----Original Message----- > From: fpc-devel [mailto:fpc-devel-boun...@lists.freepascal.org] On > Behalf Of Karoly Balogh (Charlie/SGR) > Sent: Wednesday, 27 December 2017 03:43 > To: FPC developers' list <fpc-devel@lists.freepascal.org> > Subject: Re: [fpc-devel] *** GMX Spamverdacht *** An extension of > fpc language: the BASED construct > > HI, > > On Tue, 26 Dec 2017, Thorsten Engler wrote: > > > > Item: BYTE BASED ItemPtr; > > > > Ignoring any other considerations for now, I would have at least > used > > a logical extension derived from already supported syntax: > > > > Item: Byte absolute ItemPtr^; > > As far as I understand (I did not try) this was once supported, but > explicitly removed by FPC 2.4.0 from Absolute keyword dereferencing > is no longer allowed: > > http://wiki.freepascal.org/User_Changes_2.4.0#Absolute_variable_decl > arations > > As the reasoning there shows, it's a very slippery slope this, which > could open a can of worms, so careful people. :) > > Charlie > _______________________________________________ > fpc-devel maillist - fpc-devel@lists.freepascal.org > http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
