[Solved] Possible bug in Instr or gb.IgnoreCase in Gambas 3.12.0
- Got2BeFree
- Posts: 92
- Joined: Saturday 26th November 2016 2:52am
- Location: Lost
Re: Try replacing InStr with String.InStr if code is suddenly acting strange
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).
sholzy
I'm wondering around lost in the past, not knowing where the present is.
I'm wondering around lost in the past, not knowing where the present is.
- grayghost4
- Posts: 187
- Joined: Wednesday 5th December 2018 5:00am
- Location: Marengo, Illinois usa
Re: Try replacing InStr with String.InStr if code is suddenly acting strange
I tried to install 3.12 on my Fedora laptop computer .. but it will not configure or make .... many errors.
- cogier
- Site Admin
- Posts: 1126
- Joined: Wednesday 21st September 2016 2:22pm
- Location: Guernsey, Channel Islands
Re: Try replacing InStr with String.InStr if code is suddenly acting strange
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
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
Re: Try replacing InStr with String.InStr if code is suddenly acting strange
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.
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.