Re: [fpc-pascal] Class field property access

2019-06-07 Thread Ryan Joseph
> On Jun 7, 2019, at 8:08 AM, Sven Barth via fpc-pascal > wrote: > > Only because this example appears safe does not mean that the whole concept > is safe. > A class might initialize b only later on and with a direct property you'll > only get an access violation. So you'll need a getter any

Re: [fpc-pascal] http://wiki.freepascal.org/ web site is totally blank

2019-06-07 Thread wkitty42
On 6/7/19 11:05 AM, Dennis wrote: DaWorm wrote: There was a thread yesterday about issues with the servers.  This may be related. The web site is still blank. it'll continue to be ""blank"" until they get everything moved to a new server, too... -- NOTE: No off-list assistance is give

Re: [fpc-pascal] http://wiki.freepascal.org/ web site is totally blank

2019-06-07 Thread Dennis
DaWorm wrote: There was a thread yesterday about issues with the servers.  This may be related. Jeff On Thu, Jun 6, 2019 at 4:58 AM Dennis > wrote: Does it only happen to me? The web site is still blank. Dennis __

Re: [fpc-pascal] Class field property access

2019-06-07 Thread Sven Barth via fpc-pascal
Ryan Joseph schrieb am Fr., 7. Juni 2019, 14:00: > > > > On Jun 7, 2019, at 2:51 AM, Michael Van Canneyt > wrote: > > > > What kind of behaviour are you referring to. > > Something wrong with my mail server causing your server to block me (Jonas > said my server didn’t handle greylisting correct

Re: [fpc-pascal] Class field property access

2019-06-07 Thread Ryan Joseph
> On Jun 7, 2019, at 2:51 AM, Michael Van Canneyt > wrote: > > What kind of behaviour are you referring to. Something wrong with my mail server causing your server to block me (Jonas said my server didn’t handle greylisting correctly). Easier to just re-sub using gmail for now. > >> Who c

Re: [fpc-pascal] Class field property access

2019-06-07 Thread Sven Barth via fpc-pascal
Michael Van Canneyt schrieb am Fr., 7. Juni 2019, 08:52: > > This appears to be a regression since 3.0.4 also. Did you specifically > > disable this in 3.3.1? Sorry I’m not understanding this one. > > If it was allowed in previous versions, this was by accident allowed during > parsing and most