Hello Seighard.
Thanks for that clear explanations.
By the way, I did check in all the msegui sources if there was, by bad
chance, a other case with omitted parenthesis in "is" operator combined with
"and".
In all the code written by Martin, when "is" is used with "and", the
parenthesis are
Hello fredvs,
you wrote on Mon, 9 Mar 2020 02:00:30 -0700 (MST):
> > I'd rather suggest parentheizing the first partial expression, like so:
> > if (fld1 is tblobfield) and (self.fblobintf <> nil) then begin
>
> Yes, it is exactly what was proposed in fpc mailing list.
>
> It is also what
Re-hello Code DZ.
> I tried fixing these warning but i lost .
What makes you stop, what kind of warnings?
Fre;D
--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/
___
mseide-msegui-talk mailing list
Hello Code dz
> i think msegui should stay with fpc3.0.4 until finding the fix
Yes, of course, fpc 3.0.4 is the "official" last release of fpc.
I do regularly check the new features of fpc 3.3.1 trunk, this to not be too
far of what appends.
(And I agree also to check if ,by chance, they fixed
On 09/03/2020 9:00 am, fredvs wrote:
>> I'd rather suggest parentheizing the first partial expression, like so:
>> if (fld1 is tblobfield) and (self.fblobintf <> nil) then begin
> Yes, it is exactly what was proposed in fpc mailing list.
Nice, good catch Sieghard.
Regards,
Graeme
Hi fred. I tried fixing these warning but i lost . i think msegui should
stay with fpc3.0.4 until finding the fix .
On 8 Mar 2020 14:11, "fredvs" wrote:
> Re-hello.
>
> OK, I did apply the Graemes's fix: adding {$interfaces corba}, just after
> unit msedbusinterface.
>
> This fixes the error:
>
Hello Sieghard.
> I'd rather suggest parentheizing the first partial expression, like so:
> if (fld1 is tblobfield) and (self.fblobintf <> nil) then begin
Yes, it is exactly what was proposed in fpc mailing list.
It is also what I did commit in mse-org/mseide_msegui
7 matches
Mail list logo
