Page 2 of 2

Re: Try replacing InStr with String.InStr if code is suddenly acting strange

Posted: Thursday 3rd January 2019 6:23pm
by Got2BeFree
This is a Gambas bug. The problem exits on openSUSE Leap 15 also. Worked ok with Gambas 3.11.x, but not with 3.12.x. I imagine it will also fail on my Debian 9.6 box if I were to upgrade Gambas from 3.11.x to 3.12.x (update not in my repo yet).

Re: Try replacing InStr with String.InStr if code is suddenly acting strange

Posted: Thursday 3rd January 2019 8:45pm
by grayghost4
I tried to install 3.12 on my Fedora laptop computer .. but it will not configure or make .... many errors. 8-)

Re: Try replacing InStr with String.InStr if code is suddenly acting strange

Posted: Friday 4th January 2019 12:36pm
by cogier
I put up a bug report on the Mailing list pointing to this thread and received the following: -

Le 03/01/2019 à 17:34, Charlie Ogier a écrit :
Hi Benoît,

Have a look at this thread
https://forum.gambas.one/viewtopic.php? ... 1383#p1383

Charlie


It has been fixed in the last commit. I will release a 3.12.1 version as
soon as possible.

Regards,

Benoît Minisini


Sorted :D

Re: Try replacing InStr with String.InStr if code is suddenly acting strange

Posted: Saturday 5th January 2019 8:31am
by Godzilla
cogier thank you for bringing this to Benoît Minisini's attention. I'm glad he's on it, and happy to hear that the fix is already coded and will be in the upcoming release.

String.InStr will suffice for everyone who upgraded to in 3.12.0, for code that must be relied on until then. I'll see if I can edit this thread's title, preface it with [Solved], and change it to your mailing list title so it makes more sense.