Re: [fpc-pascal] Operator overload bug

2018-08-04 Thread Ryan Joseph
> On Aug 4, 2018, at 8:38 AM, Sven Barth via fpc-pascal > wrote: > > Nevertheless I fixed the problem in r39554. Thanks Sven. Regards, Ryan Joseph ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-

Re: [fpc-pascal] Operator overload bug

2018-08-04 Thread Sven Barth via fpc-pascal
On 04.08.2018 17:31, Ben Grasset wrote: > On Sat, Aug 4, 2018 at 10:38 AM, Sven Barth via fpc-pascal > > wrote: > > On 28.07.2018 16:38, John Doe wrote: > > On Mon, Jul 23, 2018 at 1:49 PM, Sven Barth via fpc-pascal > >

Re: [fpc-pascal] Operator overload bug

2018-08-04 Thread Ben Grasset
On Sat, Aug 4, 2018 at 10:38 AM, Sven Barth via fpc-pascal < fpc-pascal@lists.freepascal.org> wrote: > On 28.07.2018 16:38, John Doe wrote: > > On Mon, Jul 23, 2018 at 1:49 PM, Sven Barth via fpc-pascal > > > > wrote: > > > > Ryan Joseph >

Re: [fpc-pascal] Operator overload bug

2018-08-04 Thread Sven Barth via fpc-pascal
On 28.07.2018 16:38, John Doe wrote: > On Mon, Jul 23, 2018 at 1:49 PM, Sven Barth via fpc-pascal > > wrote: > > Ryan Joseph > schrieb am Mo., 23. Juli 2018, > 17:35: > > > > On Jul 23, 2018, at 12:0

Re: [fpc-pascal] Operator overload bug

2018-07-31 Thread Ben Grasset
It's still open by my view, with "new" status: https://bugs.freepascal.org/view.php?id=34021 On Tue, Jul 31, 2018 at 11:47 AM, Ryan Joseph wrote: > > > > On Jul 30, 2018, at 4:11 PM, Ben Grasset wrote: > > > > If you don't have an SVN patch utility handy you could probably just > look at it an

Re: [fpc-pascal] Operator overload bug

2018-07-31 Thread Ryan Joseph
> On Jul 30, 2018, at 4:11 PM, Ben Grasset wrote: > > If you don't have an SVN patch utility handy you could probably just look at > it and apply it to your sources yourself. The final version looks like it's > just two lines changed in a single file. Thanks for fixing that Ben. I don’t have

Re: [fpc-pascal] Operator overload bug

2018-07-30 Thread Ben Grasset
By looks like I meant, "is", not sure why I wrote that. (I'm Akira1364, by the way.) On Mon, Jul 30, 2018 at 6:11 PM, Ben Grasset wrote: > If you don't have an SVN patch utility handy you could probably just look > at it and apply it to your sources yourself. The final version looks like > it's

Re: [fpc-pascal] Operator overload bug

2018-07-30 Thread Ben Grasset
If you don't have an SVN patch utility handy you could probably just look at it and apply it to your sources yourself. The final version looks like it's just two lines changed in a single file. On Mon, Jul 30, 2018 at 11:29 AM, Ryan Joseph wrote: > > > > On Jul 28, 2018, at 8:38 AM, John Doe >

Re: [fpc-pascal] Operator overload bug

2018-07-30 Thread Ryan Joseph
> On Jul 28, 2018, at 8:38 AM, John Doe wrote: > > Someone posted a working patch for this on the bugtracker report Ryan made, > just to let you know. Thanks, what do we do now? The patch is sitting there but how does it get applied? https://bugs.freepascal.org/view.php?id=34021 Regards,

Re: [fpc-pascal] Operator overload bug

2018-07-28 Thread John Doe
On Mon, Jul 23, 2018 at 1:49 PM, Sven Barth via fpc-pascal < fpc-pascal@lists.freepascal.org> wrote: > Ryan Joseph schrieb am Mo., 23. Juli 2018, > 17:35: > >> >> > On Jul 23, 2018, at 12:00 AM, Sven Barth via fpc-pascal < >> fpc-pascal@lists.freepascal.org> wrote: >> > >> > Yes, it's a bug, so p

Re: [fpc-pascal] Operator overload bug

2018-07-23 Thread Sven Barth via fpc-pascal
Ryan Joseph schrieb am Mo., 23. Juli 2018, 17:35: > > > > On Jul 23, 2018, at 12:00 AM, Sven Barth via fpc-pascal < > fpc-pascal@lists.freepascal.org> wrote: > > > > Yes, it's a bug, so please report it. > > Thanks, reported. The severity is “minor” which I guess is correct. > "Minor" is the def

Re: [fpc-pascal] Operator overload bug

2018-07-23 Thread Ryan Joseph
> On Jul 23, 2018, at 12:00 AM, Sven Barth via fpc-pascal > wrote: > > Yes, it's a bug, so please report it. Thanks, reported. The severity is “minor” which I guess is correct. https://bugs.freepascal.org/view.php?id=34021 Regards, Ryan Joseph _

Re: [fpc-pascal] Operator overload bug

2018-07-22 Thread Sven Barth via fpc-pascal
Ryan Joseph schrieb am So., 22. Juli 2018, 18:11: > I mentioned this as an aside a while ago but I don’t remember getting a > response so I’d like to formally reintroduce the issue. > > Should I file a bug report for this or is it expected behavior? Personally > I’d really like to get implicit ar

Re: [fpc-pascal] Operator overload bug

2018-07-22 Thread Ryan Joseph
> On Jul 22, 2018, at 6:22 PM, Ben Grasset wrote: > > Also, one other thing: you should really be specifying the right-hand-side > array parameter as "const" there. If you don't, it will be copied in its > entirety instead of being passed by reference. Basically just always pass > everything

Re: [fpc-pascal] Operator overload bug

2018-07-22 Thread Ben Grasset
gt; > > ______________ > > Od: Ben Grasset > > Komu: FPC-Pascal users discussions > > Datum: 23.07.2018 02:16 > > Předmět: Re: [fpc-pascal] Operator overload bug > > > I'd say it's a bug in the sense tha

Re: [fpc-pascal] Operator overload bug

2018-07-22 Thread Vojtěch Čihák
-Pascal users discussions Datum: 23.07.2018 02:16 Předmět: Re: [fpc-pascal] Operator overload bug I'd say it's a bug in the sense that the compiler assumes something starting with "[" and ending with "]" can only possibly be a set in that context. On Sun, Jul 22,

Re: [fpc-pascal] Operator overload bug

2018-07-22 Thread Ben Grasset
Also, one other thing: you should *really* be specifying the right-hand-side array parameter as "const" there. If you don't, it will be copied in its entirety instead of being passed by reference. Basically just always pass everything as "const" (or "constref" if it's specifically a record) unless

Re: [fpc-pascal] Operator overload bug

2018-07-22 Thread Ben Grasset
I'd say it's a bug in the sense that the compiler assumes something starting with "[" and ending with "]" can only possibly be a set in that context. On Sun, Jul 22, 2018 at 12:10 PM, Ryan Joseph wrote: > I mentioned this as an aside a while ago but I don’t remember getting a > response so I’d l