SplitString issue

[Curt Carpenter]

I am using Lazarus 3.2 in a simple FPC program on Linux.  Very briefly, I have code something like this:

Code: Pascal  [Select][+][-]

1. var
2.   Message: TStringArray;
3.   S: string;
4.   ...
5.  
6. begin
7.   S := 'A,B,C';
8.   Message := SpitString(S,',');
9.   ...
10.  
11. end;
12.  

I've discovered that rather than the TStringArray Message containing  the items A,B and C it contains 'A'#$0A, 'B'#$0A,'C'#0A
according to my Watches -- that is, each element has an appended line feed.   Is there a way to eliminate the line feeds?  I have a similar use of TString Array and StringSplit in a Lazarus GUI application and the line feeds don't seem to appear there.  Or are the single quote characters and the line feed an artifact of the Watch window?

Thanks.
 

[cdbc]

Hi
Curt, you can do better than that...

Code: Pascal  [Select][+][-]

1. A,B,C;

...are they constants, variables or something from scrabble?!?

Code: Pascal  [Select][+][-]

1. S:= 'A,B,C'; { if you want a string }
2. S:= A + ',' + B + ',' + C; { if they're consts or vars}

Write us a piece of code that makes sense, NONE of us can read minds 
Regards Benny

[Curt Carpenter]

Hi
Curt, you can do better than that...

Yes, sorry:  added the single quotes in the OP.  Been working on this problem all morning and think I'm going blind.  Probably need a break.  Other problems in the OP too -- will come back later after a walk.

[Martin_fr]

I've discovered that rather than the TStringArray Message containing  the items A,B and C it contains 'A'#$0A, 'B'#$0A,'C'#0A
according to my Watches -- that is, each element has an appended line feed.

I just tried that on Windows Win10 64 bit => no linefeeds

Lazarus 4.99 (in case the older IDE messed up watches / not that I recall any such bug)
FPC 3.2.2 and 3.2.3 (both tested)

[Curt Carpenter]

Yes, it was me.  The string wasn't 'A,B,C' but 'A,B,C#10"  as received -- so my OP messed up in multiple regards. 

[VisualLab]

I also checked the given example (Lazarus 3.4, Windows 10 64-bit). Degugger works correctly, as expected, even though I use an older IDE

[Martin_fr]

2 things though about the debugger.

1) Which one did you @Curt Carpenter use? Gdb or FpDebug
2) Which setting for debug info? Dwarf 2 or 3?

There may be an odd version of gdb doing something odd....

But also, if you use Dwarf 2 (that is Dwarf, or dwarf-with-sets / anything NOT labelled "dwarf 3"), then FPC does write strings in a form that is not distinguishable from Pchar. 
Though even then
- there would be 'a'#0  Strings always have a leading #0 byte
- FpDebug would display 2 results labelled string and pchar.

But of course, I don't know what the odd version of GDB would do.


--------EDIT
Just saw you found something else...

[MarkMLl]

- there would be 'a'#0  Strings always have a leading #0 byte

Leading?

MarkMLl

[Martin_fr]

- there would be 'a'#0  Strings always have a leading #0 byte

Leading?

RTL (right to left) ordering...

[MarkMLl]

RTL (right to left) ordering...

Ah. Just like APL: parses LTR then evaluates RTL.

Let's not go there, Curt's smart enough to work it out :-)

MarkMLl

[Thaddy]

Besides, a stringarray is not a chararray and strings always have a termination zero even if they are just one character long.

[Curt Carpenter]

No no -- the whole problem was down to me not being careful and making assumptions about what was going on.  Everything is working fine.  Should have taken that walk before I posted here -- sorry.