Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

2020-03-29 Thread fredvs
Hello Seignard. > Yes I was thinking to do that but it is **lot of work**, +- 500 cases to > fix, sometimes in complicated code. It was terminated yesterday, after lot of cups of coffee, checking every case individually and following your advice: adding a last else statement + comment. > else;

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

2020-03-29 Thread Sieghard
Hello fredvs, you wrote on Fri, 27 Mar 2020 18:30:11 -0700 (MST): > I can understand that in a case of the variable is part of the procedure, > like this: ... > begin > case b of // here warning > 1: writeln('hello'); > end > end; ... > But for this, when the variable is

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

2020-03-29 Thread Sieghard
Hello fredvs, you wrote on Sun, 29 Mar 2020 08:36:10 -0700 (MST): > So, about those famous 2 last warnings: > > I propose this to make the compiler happy: ... > > msedatalist.pas(891,18) Warning: (4110) Range check error while > > evaluating constants (-193 must be between 0 and 255) > >

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

2020-03-29 Thread fredvs
The same for the last warning: Changing with this: modmask = abs(shift or ctrl or alt or $1000 or pad); ... result:= (key <> 0) and (key <> word((not modmask))); Gives the warning: mseactions.pas(763,34) Warning: (4110) Range check error while evaluating constants (-63489 must be between 0 and

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

2020-03-29 Thread fredvs
What is very strange is that I get also a warning with this (see abs() added): const foldhiddenbit = 7; foldhiddenmask = abs(1 shl foldhiddenbit); currentfoldhiddenbit = 6; currentfoldhiddenmask = abs(1 shl currentfoldhiddenbit); foldlevelmask = byte(not (foldhiddenmask or

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

2020-03-29 Thread fredvs
> why not just replace byte with integer I just try it and with this you get 8 new warnings... -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

2020-03-29 Thread code dz
why not just replace byte with integer , i am not sure ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

2020-03-29 Thread code dz
why not just replace byte with integer , i am not sure ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

2020-03-29 Thread fredvs
Sorry I am a never-give-it-up... So, about those famous 2 last warnings: I propose this to make the compiler happy: - First warning: > msedatalist.pas(891,18) Warning: (4110) Range check error while evaluating > constants (-193 must be between 0 and 255) Point to: foldlevelmask =