lining up numbers in columns

[FellippeHeitor]

Wait, where did I get this idea of there being a space on the right of a STR$(number)?

No idea :-)

[bplus]

Ah! from this:

Code: QB64: [Select]

1. print "Here is a number";26;"and here is another";len("Mark");", any spaces on the right side?"

[Pete]

_TRIM it is :-)

Oh, you mean you are THINKING about making that a keyword. I wish you would have stated that in the first place, because Ive been running all through the wiki, looking for _TRIM!

Pete :D

Based on a spoof from a TV series: Hey June, where's Ward? He's running all over town looking for Beaver!

Seriously, it would save typing two keywords, like LTRIM$(STR$()) and LTRIM$(RTRIM$()), and should be a snap to implement. Nothing like the FN hell you'd have to go through to implement FN.

[FellippeHeitor]

_TRIM$() is already available in the development builds and will make it to the wiki as soon as 1.3 is released ;-)

More on what's coming up here: https://www.qb64.org/forum/index.php?topic=304.msg2554#msg2554

[bplus]

"Print using" does not work? http://qb64.org/wiki/PRINT_USING

It is really an excellent idea. Welcome to the forum RadoiHactive!

[Jack002]

Years ago I would make a fn called trim that was rtrim and ltrim together. I assume this is what we're discussing?

STR$ will make a space to the left of the number. I have often done a mid$ 2 of it just to zap it. Trim also works.

[Pete]

STR$() actually doesn't make the space. The space is already there. It just doesn't get rid of it. Try print 1. You'll see the 1 is indented one space to the left. Now try print 2. You see the - sign is on the margin, followed by the 1. So the computer language just formats numbers in this manner, preserving a space in case a negative is involved. At least that's my non-schooled take on the matter. As the the trailing space that STR$() does trim off, well, I used to know what that was for, but I have to admit, I've forgotten!

Pete