StringSplit - strange behavior ? or bug ?

[JohnOne]

This seem wrong too.

#include <Array.au3>
Local $sData1 = "0AB1Ab2aB3ab4Ab5AB6"

Local $aTest1 = StringSplit($sData1, "ab")
_ArrayDisplay($aTest1, '$aTest1')

[mLipok]

is it the same with my last repro ?

Local $aTest1 = StringSplit($sData1, 'ab', 1)
_ArrayDisplay($aTest1, '$aTest1')
#cs Current AutoIt 3.3.11.3 Results :
    Row|Col 0
    [0]|2
    [1]|0AB1Ab2
    [2]|3
#CE
#CS expected result :
    Row|Col 0
    [0]|2
    [1]|0AB1Ab2aB3
    [2]|4Ab5AB6
#CE

[mikell]

Your new example in post #19 test is very synthetic and explicit, OK for me 

IMHO you should ask a Mod or Dev for deletion of the old ticket (too much modifications will be confusing, and the title doesn't match) and then write a new one

Edited March 14, 2014 by mikell

[mLipok]

  On 3/14/2014 at 12:34 PM, mikell said:

Your new example in post #19 test is very synthetic and explicit, OK for me 

Thank you. 

btw. Well said;) 

 

 

  On 3/14/2014 at 12:34 PM, mikell said:

IMHO you should ask a Mod or Dev for deletion of the old ticket (too much modifications will be confusing, and the title doesn't match) and then write a new one

 

This basically were short entries, so that the scripts were long. 

On the other hand, I am not a supporter of hiding my own errors, yet on them, we humans are learning. 

But I have a distance to my own person, so I can notice my own mistakes and admit to them. 

 

Therefore, please see TrackTicket.

 

And thank you once again for your participation.

[JohnOne]

  On 3/14/2014 at 12:22 PM, mLipok said:

 

is it the same with my last repro ?

Local $aTest1 = StringSplit($sData1, 'ab', 1)
_ArrayDisplay($aTest1, '$aTest1')
#cs Current AutoIt 3.3.11.3 Results :
    Row|Col 0
    [0]|2
    [1]|0AB1Ab2
    [2]|3
#CE
#CS expected result :
    Row|Col 0
    [0]|2
    [1]|0AB1Ab2aB3
    [2]|4Ab5AB6
#CE

Nope, even weirder.

[mLipok]

  On 3/14/2014 at 1:35 PM, JohnOne said:

Nope, even weirder.

 

Indeed strange. 

 

Basically I knew about this problem about 2 months, and it is because one of the scripts stopped working properly, but I had no creativity to a depth check, because the script is large and very complicated. 

 

It was not until the development of the related project (the new debugging system), I came across a strange-looking data/information.

[JohnOne]

would be nice for an optional fourth parameter for case sensitivity.

[mLipok]

You mean : to disable case sensitivity ?

Good idea.

I think it's worth report it right away, because if Jon will take on, it is possible to "kill two birds with one stone" (translation is not such as I would have liked). 

 

So do the honors, and create a new Track Ticket.

 

 

 

from HelpFile:

  Quote

 

delimiters One or more characters to use as delimiters (case sensitive).

[Melba23]

mLipok,

I have amended the ticket title to reflect the (very interesting) discussion above:

StringSplit - bug : Delimiter case sensitivity problem

M23

[guinness]

  On 3/14/2014 at 9:13 AM, czardas said:

This bug has been around for at least the last two stable releases. I'm amazed it hasn't been reported until now.

If you knew about it why didn't you report it?

[Melba23]

guinness,

I understood that to mean that czardas had tested the script on those earlier releases this morning and found that they too have this problem - not that he has known about the bug since their release date.

M23

[guinness]

  On 3/14/2014 at 3:50 PM, Melba23 said:

guinness,

I understood that to mean that czardas had tested the script on those earlier releases this morning and found that they too have this problem - not that he has known about the bug since their release date.

M23

If that is the case then my sincere apologies.

[mLipok]

 

  On 3/14/2014 at 3:15 PM, Melba23 said:

mLipok,

I have amended the ticket title to reflect the (very interesting) discussion above: 

StringSplit - bug : Delimiter case sensitivity problem

M23

 

Thanks.

 

btw:

JohnOne look here: #2672

[czardas]

  On 3/14/2014 at 3:50 PM, Melba23 said:

guinness,

I understood that to mean that czardas had tested the script on those earlier releases this morning and found that they too have this problem - not that he has known about the bug since their release date.

M23

 

Correct.

[mikell]

  On 3/14/2014 at 1:18 PM, mLipok said:

But I have a distance to my own person, so I can notice my own mistakes and admit to them.

Well, who never does mistakes ? not me certainly 

I said this only in order to have a ticket as clear and compact as possible (as required in the Trac rules)

Anyway it's now nicely explained