Re: Hmm... 30.20.2 dropped backward compatibility?

[Admin <admin@xxxxxxxxxx>]

13.10.2025 20:03, Benoît Minisini пишет:
> Le 13/10/2025 à 14:54, Admin a écrit :
> > I tried that. Indeed OpenSuSE version 3.20.99 worked. But what about 
> > official repos? 
>
> Did you try the stable packages from OpenSuSE Build Server as well?

No. I'm not sure how do I do that. The instructions just tell how to add 
a repository, which leads to 'apt install gambas3' installing 3.20.99 
version and it works


> > Well, I fixed the problem by specifying the exact bytecode, in my 
> > case - 3.15, those binaries work with official debian repo version 
> > 3.20.2-1. 
>
> Do you mean that by forcing the bytecode of your project, it does not 
> raise the error anymore?

Yes, forcing the bytecode and compiling a binary fixes the problem, 
program starts, no errors in console. By the way, I am forcing only 
bytecode version 3.15, and those binaries that did not start were 
compiled using version 3.15.2. So, basically I would expect the bytecode 
to be the same with or without the environment setting, but no, If I 
compile a project using gambas 3.15.2, it does not run on 3.20.2, but if 
I compile the project using gambas 3.15.2 forcing 3.15 bytecode, it runs 
on 3.20.2 flawlessly.


> > Since reinstalling Gambas on all Debian13 machines is not really a 
> > sutable way, this fix is good enough. I just wonder If this is 
> > intentional and if it will change in the future.
>
> No, I don't understand what happens with your project, and why you get 
> this error on a line that does not raise an error.
>
> If you can try with the 3.20 packages from OpenSuSE Build Servers, I 
> will know if the problem is actually in the packages made by Debian or 
> not.


Well, I'll try.


> Thanks in advance.