Hello.

With fpc 3.3.1 there is this warning:

"Warning: (4110) Range check error while evaluating constants (-193 must be between 0 and 255)"

Here the code pointed by the warning:

const
 foldhiddenbit = 7;
 foldhiddenmask = 1 shl foldhiddenbit;
 currentfoldhiddenbit = 6;
 currentfoldhiddenmask = 1 shl currentfoldhiddenbit;
 foldlevelmask = byte(not (foldhiddenmask or currentfoldhiddenmask));
-------->Here the warning

I dont understand how the compiler can find -193 as value for foldlevelmask...

Fre;D

-----
Many thanks ;-)

so let's work through it manually... with a little rambling because too much c0ffee...

foldhiddenmask is 10000000 binary (128 decimal; 80 hex) currentfoldhiddenmask is 01000000 binary (64 decimal; 40 hex)

ORing them gives 11000000 binary (192 decimal; c0 hex) applying the NOT gives 00111111 binary (63 decimal; 3f hex)

so that seems to come out as expected but i found several online bitwise calculators that came with the same -193 answer that fpc returned... this seems to be related to a wrong field initialization of some kind or using the wrong size for the value...

go here: http://easyonlineconverter.com/converters/bitwise-calculator.html place 11000000 in field 1
leave field 2 blank
select "NOT"
click calculate

this one, https://toolslick.com/math/bitwise/not-calculator , gives the same -193 result but you can also see that it is using 16 bits (word) instead of 8 bits (byte) so the top 8 zero bits are also NOTted which makes them ones and there's the error... 1111111100111111 == -193... so i tried to trick it and used 16bits... damned thing prepended 8 more ones to the beginning... they're not respecting that this is a byte we're working with...

i almost feel like telling both of them and the others i found that their calculators are broken pretty badly... so back to your immediate problem...

apparently your byte() is not working as desired?

perhaps byte() is in the wrong place? perhaps it should be
   foldlevelmask = not (byte(foldhiddenmask) or byte(currentfoldhiddenmask));

perhaps the top 8 bits need to be cleared by forcing them to zeros somehow if the default size of a const is larger than a byte?

perhaps it should be specified that all four of foldhiddenbit, foldhiddenmask, currentfoldhiddenbit, currentfoldhiddenmask are of byte instead of word or other?

const
   foldhiddenbit : byte = 7;
   foldhiddenmask : byte = 1 shl foldhiddenbit;
   currentfoldhiddenbit : byte = 6;
   currentfoldhiddenmask : byte = 1 shl currentfoldhiddenbit;
   foldlevelmask : byte = not (foldhiddenmask or currentfoldhiddenmask);
*or*
   foldlevelmask : byte = not (byte(foldhiddenmask) or byte(currentfoldhiddenmask));

NOTE: i do not currently have FPC (or lazarus) installed so i haven't tested this in fpc... i needed some drive space a few weeks back and it was easiest to remove fpc and lazarus at the time... especially since i had four or five versions of each installed with full source code...

Yes, those constants are defaulting to integer, which can represent both negative and positive values. When you do your shl you're inadvertently causing them to go into the range that pascal thinks is negative.

The typed constant should fix it.

Hello WKitty.

   foldhiddenmask : byte = 1 shl foldhiddenbit;
   currentfoldhiddenmask : byte = 1 shl currentfoldhiddenbit;
   foldlevelmask : byte = not (foldhiddenmask or currentfoldhiddenmask);
  =
  msedatalist.pas(897,47) Error: (3203) Illegal expression
  msedatalist.pas(899,61) Error: (3203) Illegal expression
  msedatalist.pas(900,72) Error: (3203) Illegal expression

Thanks for the links for calculation, indeed the result is -193.

I did play with abs(), for example:

foldlevelmask = abs(byte(not (foldhiddenmask or currentfoldhiddenmask)));

But strangely still that warning:
Warning: (4110) Range check error while evaluating constants (-193 must be between 0 and 255)

Fre;D

Fre;D

-----
Many thanks ;-)

just to be clear.. you did do foldhiddenbit: byte = 7, etc?

Hello Alexander.

I did:

const
   foldhiddenbit : byte = 7; // line 896
   foldhiddenmask : byte = 1 shl foldhiddenbit; // line 897
   currentfoldhiddenbit : byte = 6; // line 898
   currentfoldhiddenmask : byte = 1 shl currentfoldhiddenbit; // line 899
   foldlevelmask : byte = not (foldhiddenmask or currentfoldhiddenmask); //
line 900

That gives that error messages:

msedatalist.pas(897,47) Error: (3203) Illegal expression
msedatalist.pas(899,61) Error: (3203) Illegal expression
msedatalist.pas(900,72) Error: (3203) Illegal expression
msedatalist.pas(1126,1) Fatal: (10026) There were 3 errors compiling module,
stopping

Fre;D

-----
Many thanks ;-)

And only changing this:

foldhiddenbit: byte = 7;

Gives also a error message on next line unchanged:

foldhiddenmask = 1 shl foldhiddenbit; // raise a error on that line.

Error: (3203) Illegal expression

Fre;D

-----
Many thanks ;-)

And doing this:

 foldhiddenbit = byte(7);
 foldhiddenmask = byte(1 shl foldhiddenbit);
 currentfoldhiddenbit = byte(6);
 currentfoldhiddenmask = byte(1 shl currentfoldhiddenbit);
 foldlevelmask = abs(byte(not (foldhiddenmask or currentfoldhiddenmask)));
// line 891

Gives also a warning:
msedatalist.pas(891,22) Warning: (4110) Range check error while evaluating constants (-193 must be between 0 and 255)

OK, I stop.

Fre;D

-----
Many thanks ;-)

This make the compiler happy:

foldlevelmask = byte(abs(not (foldhiddenmask or currentfoldhiddenmask)));

Not sure it is better to do abs() but so no more warning.

Let's fix with it?

-----
Many thanks ;-)

PM fredvs wrote

OK, I stop.

This works?

{$mode objfpc}
{$apptype console}
const
  foldhiddenbit = byte(7);
  foldhiddenmask = byte(1 shl foldhiddenbit);
  currentfoldhiddenbit = byte(6);
  currentfoldhiddenmask = byte(1 shl currentfoldhiddenbit);
  intermediate = word(byte(foldhiddenmask) or byte(currentfoldhiddenmask));
  intermediate2 = Word(not intermediate);
  foldlevelmask = byte(lo(intermediate2)); //byte(not
(byte(foldhiddenmask) or byte(currentfoldhiddenmask)));
begin
  writeln('intermediate=',intermediate);
  writeln('foldlevelmask=',foldlevelmask);
end.

Prints:
intermediate=192
foldlevelmask=63

you should figure out why typed constants are not being allowed/used in your setup...

https://wiki.freepascal.org/Constants#Scalar_constants https://www.freepascal.org/docs-html/ref/refse10.html

also, what mode are you compiling with? that may be tripping this up if the current mode doesn't allow typed constants...

what mode are you compiling with?

{$mode objfpc}{$h+}

-----
Many thanks ;-)

perhaps calculate those results by hand and assign them.. then fix it later? hehe

perhaps calculate those results by hand and assign them.. then fix it

later? hehe

Yes, that is the thing with the gurus, it must seem complicated.

I agree that writing this:

foldlevelmask = byte(not (foldhiddenmask or currentfoldhiddenmask));

is much more impressive than writing this:

foldlevelmask = -193

;-)

-----
Many thanks ;-)

what about

 foldlevelmask = (not (foldhiddenmask or currentfoldhiddenmask)) and $ff ;
instead of the "  f...  := byte(...) " line

?

what about foldlevelmask = (not (foldhiddenmask or currentfoldhiddenmask)) and $ff ;

Ha, this one fpc 3.3.1 like it!

No more warning nor error.

May I ask you what "and $ff" does, is it the same as "abs()" or keep it the negative value?

Many thanks.

Fre;D

-----
Many thanks ;-)

z := x AND y is a bitwise AND

(not (foldhiddenmask or currentfoldhiddenmask))

results in

dec: -193 hex: ffff ff3f bin: 1111 1111 1111 1111 1111 1111 0011 1111

this AND hex: $ff (bin: 11111 1111) gives

bin: 1111 1111 1111 1111 1111 1111 0011 1111
AND
bin: 0000 0000 0000 0000 0000 0000 1111 1111
-------------------------------------------------------------------- bin: 0000 0000 0000 0000 0000 0000 0011 1111

the result now definitely fits in a byte

The operators NOT, AND, OR, XOR (applied to integers) should be mentioned somewhere in the documentation, maybe the explanation there is clearer

Many thanks Gerhald.

Now I have to deeply study your code, I did not catch all at first glance.

Write you later.

Fre;D

-----
Many thanks ;-)

schrieb am Di., 24. März 2020, 18:37:

Typed constants can not be used to initialize constants.

Regards,
Sven

Splitting the last constant a bit more allows to find the culprit:

=== code begin ===
const
   const1 = foldhiddenmask or currentfoldhiddenmask;
   const2 = not const1;
   const3 = byte(not const2);

=== code begin ===

The compiler will now complain on const3 (and a check with SizeOf(...) reveils that const2 is not of Byte size). I'll have to investigate however why the "not" behaves as it does.

Regards,
Sven

hummm... ok, so how to you get a constant to be a byte and storing 7 for the decimal value?

or are you saying that you cannot use a typed constant in the init of another (typed) constant?

schrieb am Mi., 25. März 2020, 18:47:

The compiler normally uses the smallest possible type that can represent the value. You can force it however by using e.g.

const
  MyConst = Word(42);

or are you saying that you cannot use a typed constant in the init of another (typed) constant?

Correct.

Regards,
Sven

Try
const
   seven = Byte(7);

ok... so in the situation this thread is covering:

const
   foldhiddenbit = byte(7);
   foldhiddenmask = byte(1 shl foldhiddenbit);
   currentfoldhiddenbit = byte(6);
   currentfoldhiddenmask = byte(1 shl currentfoldhiddenbit);
   foldlevelmask = byte(not (foldhiddenmask or currentfoldhiddenmask));

is the way to do it?

> or are you saying that you cannot use a typed constant in the init of another > (typed) constant? Correct.

strange...

[wargames] seems like the winning move is to not play the game. [/wargames] LUL

PM wrote

[wargames] seems like the winning move is to not play the game. [/wargames] LUL

LUL ??
What does that stand for?

Better not say that to someone who speaks Dutch (like me) ;-))

it is the LOL emoticon with a beard... i've gotten to where i use it all the time instead of plain old lol... especially since i am bearded these days ;)

Better not say that to someone who speaks Dutch (like me) ;-))

what? you don't like laughing bearded guys?

https://knowyourmeme.com/memes/lul

schrieb am Mi., 25. März 2020, 19:48:

In theory, yes, but for some reason the "not" upsets this. I have yet to investigate why though and whether this is by design.

Regards,
Sven

PM wrote

what? you don't like laughing bearded guys?

LUL means penis (and I'm putting it nicely here) in Dutch. Google translate translates it as either asshole (anatomically rahter incorrect), cock, or prick.