[Solved] Possible bug in Instr or gb.IgnoreCase in Gambas 3.12.0

User avatar
Got2BeFree
Posts: 51
Joined: Saturday 26th November 2016 2:52am
Location: Lost

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

Post by Got2BeFree » Thursday 03rd January 2019 6:23pm

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.

User avatar
grayghost4
Posts: 27
Joined: Wednesday 05th December 2018 5:00am
Location: Concord, CA usa

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

Post by grayghost4 » Thursday 03rd January 2019 8:45pm

I tried to install 3.12 on my Fedora laptop computer .. but it will not configure or make .... many errors. 8-)

User avatar
cogier
Site Admin
Posts: 282
Joined: Wednesday 21st September 2016 2:22pm
Location: Guernsey, Channel Islands

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

Post by cogier » Friday 04th January 2019 12:36pm

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

User avatar
Godzilla
Posts: 17
Joined: Wednesday 26th September 2018 11:20am

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

Post by Godzilla » Saturday 05th January 2019 8:31am

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.

Post Reply