StringField Bugs PB573

[Saki]

StringField Bugs PB573

; Empty result

Code: Select all

string$="*aaaaaaaaaa*Hello*I*am*a*splitted*"
Debug StringField(string$, 1 , "*")

; 6 Fields - Start Index=1 - End Index=6 - With 7 it work

Code: Select all

For index = 1 To 6
 Debug StringField("*Hello*I*am*a*splitted*string*", index , "*")
 Next
 

; Index should no longer be separated as a field here - Also the parameter 7 does not fit

Code: Select all

For index = 1 To 7
 Debug StringField("*Hello*I*am*a*splitted*string", index , "*")
 Next
 

// Edit: Moved from "Bugs" to "Coding Questions" (Kiffi)

[#NULL]

no bug.

one field: "a"
two fields: "a*a"
one empty field: ""
two empty fields: "*"

; Empty result

the first field spans from the beginning of the string to the first *

; 6 Fields - Start Index=1 - End Index=6 - With 7 it work

because it has 7 fields. the first field is before the first *

and why a second topic?

[BarryG]

Not a bug. Here's a count of all the stringfields in your string:

Code: Select all

 *aaaaaaaaaa*Hello*I*am*a*splitted*
1 2          3     4 5  6 7        8

So, the first stringfield is to the left of the first asterisk, thus = nothing. Same for the last stringfield.

Here's an alternative way to do what you want, by stripping the first and last asterisks:

Code: Select all

string$="*aaaaaaaaaa*Hello*I*am*a*splitted*"
Debug StringField(Trim(string$, "*"), 1 , "*") ; Returns "aaaaaaaaaa"

[NicTheQuick]

Why do you post it again? You got all the explanation already here: viewtopic.php?f=13&t=77182

[Olli]

Saki needed two versions of explanations.
It is a new technic to be sure !
As we participate per wave in the world, depending of the days and nights of everybody, I suppose he will ask a third version of the question in three hours !

[Saki]

They say there are no stupid questions, only stupid answers

I'm sorry I haven't had time to deal with the latest postings.
there are still other things to do.
As I wrote, I still have to look at it, because at the time was really more important things to do.

I have already found and reported many bugs.
Now I made a mistake, shame on me.
But we will survive this too.
I don't have to report bugs, I don't have to share new codes, no problem.

[mk-soft]

I do not make mistakes. It just needs a little tweaking sometimes

[Saki]

Yes, it's just annoying.
I invest a lot of timein this things, give away codes in which an infinite amount of work was invested
and then I have to listen to stupid comments for every shit.

Who makes a lot, makes many mistakes, who makes nothing, makes no mistakes.

The time comes when you decide not to make any more mistakes in the future.

[HeX0R]

The time comes when you decide not to make any more mistakes in the future.

Is that the same time, where you decide to re-enter the board as Walsaki or Sabus?

Seriously:
You made a quite stupid mistake, that happens!
Learn to live with a little mockery now

[skywalk]

Saki - please don't stop contributing
Only coders make mistakes.
Critics must wait for something to critique.
So, choose the quality of code wisely.

[Olli]

What it is sure is, a string text filter has lots of combinations.
StringField() just cut a source string with a delimiter string, and its index is one-based (1, 2, 3, ...), but not zero-based (0, 1, 2, ...).
Now if you use the delimiter string to mark your source string ("_ ... ... _"), the consequence seems to be strange, because its index becomes two-based (2, 3, 4, etc...)

"_monday_tuesday_wednesday_"

2 : monday
3 : tuesday
4 : wednesday

So, do not attach yourself to the remarks, and I think if we do such these remarks, it is because we are sure it is strange to manage a two-based index in this way. Strange but right even.

[Saki]

Well, thank you very much, we'll see.

The thing with the string field has its pitfalls.
It is squite difficult to code this function.


Here a PB based alterable version
It's just a bit different

viewtopic.php?f=12&t=77198

[BarryG]

The thing with the string field has its pitfalls.
It is squite difficult to code this function.

What's an example pitfall? It's a very simple and clear command to use. You can't make claims like that with no reason. All I've seen so far is just coding errors by you when using it (sorry to say).

[Saki]

Try to create a working code.
Then you will quickly find the pitfalls.

You can post it here then

When you've done that, i be happy to talk about it again.

You will fail (sorry to say).

[BarryG]

Try to create a working code.
Then you will quickly find the pitfalls.

I've got lots of use of StringField() in my apps and they've never had any pitfalls. The onus is on you to demonstrate any problems with it, since you're the one claiming it has flaws. I've not seen one demonstrated flaw from you yet. Even your "bug" report about it was just incorrect coding by you. Sorry, but that's the reality and you need to face it.