Hello fredvs,
you wrote on Tue, 10 Mar 2020 12:52:22 -0700 (MST):
> Hello Roland.
>
> Doing this:
>
> const
> foldhiddenbit = 7;
> foldhiddenmask = byte(1) shl foldhiddenbit;
> currentfoldhiddenbit = 6;
> currentfoldhiddenmask = byte(1) shl currentfoldhiddenbit;
> foldlevelmask = byte(not
I dont remember exactly . but i think Its about range checking .
On 9 Mar 2020 20:29, "fredvs" wrote:
> Re-hello Code DZ.
>
> > I tried fixing these warning but i lost .
>
> What makes you stop, what kind of warnings?
>
> Fre;D
>
>
>
> --
> Sent from:
Hello Roland.
Doing this:
const
foldhiddenbit = 7;
foldhiddenmask = byte(1) shl foldhiddenbit;
currentfoldhiddenbit = 6;
currentfoldhiddenmask = byte(1) shl currentfoldhiddenbit;
foldlevelmask = byte(not (foldhiddenmask or currentfoldhiddenmask));
foldissumbit = 0;
foldissummask = $01;
Hello Fred!
For this:
msedatalist.pas(891,18) Warning: range check error while evaluating
constants (-193 must be between 0 and 255)
I would try to replace "1" with "byte(1)".
const
foldhiddenbit = 7;
foldhiddenmask = byte(1) shl foldhiddenbit; // <
currentfoldhiddenbit = 6;
Hello everybody.
I think that the proposition of Code DZ is a "must be done" (first of all,
fix the Warnings at compilation using fpc 3.0.4).
Here are all the warnings while compiling mseide with fpc 3.0.4.
You may see that all the warnings are about string type conversion in
5 matches
Mail list logo
