> 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
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
> 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
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
On Thu, 6 Jun 2019, Ryan Joseph wrote:
On Jun 3, 2019, at 11:13 AM, Sven Barth via fpc-pascal
wrote:
The b field could be Nil and the class might not provide any functionality to check for that. In addition to that it's an additional indirection while records/objects merely require an of
> On Jun 3, 2019, at 11:13 AM, Sven Barth via fpc-pascal
> wrote:
>
> The b field could be Nil and the class might not provide any functionality to
> check for that. In addition to that it's an additional indirection while
> records/objects merely require an offset.
>
{ I’ve resubscribed
Ryan Joseph schrieb am Mo., 3. Juni 2019,
16:36:
> I found a restriction in properties which is a little disappointing. I get
> there’s probably some objective of safety but Pascal is a direct memory
> access language so I don’t understand why properties have this unique
> restriction when I coul
On 2019-06-03 16:01, Ryan Joseph wrote:
I found a restriction in properties which is a little disappointing. I
get there’s probably some objective of safety but Pascal is a direct
memory access language so I don’t understand why properties have this
unique restriction when I could do the same thi
I found a restriction in properties which is a little disappointing. I get
there’s probably some objective of safety but Pascal is a direct memory access
language so I don’t understand why properties have this unique restriction when
I could do the same thing using functions (pointers can’t be d
