QB64 Project: Unsigned values - no space for a sign to be output?

I would personally call this a feature, but no space is output for when there is no sign for unsigned values. I am hesitant to bring QB compatibility into this discussion because of the fact that _UNSIGNED is a QB64-specific feature.

So I guess my question is this:
Was the omission of a space for a sign when printing unsigned integers deliberate or just something that was overlooked? If it is something that was overlooked, will it be changed to make things more uniform, or is it unnecessary due to the fact that there is no reason to output a space where the sign should be because the integer will never have a sign?

Thanks! Great job on the fixes in v0.7 too! ^_^

------------------
Waiting patiently for Windows 7, XHTML 2.0, CSS 3.0, PHP 6.0, the ratification of C++0x, and the day that I can code without logic troubles.

Response Title	Author and Date
* Why would you need one? Perhaps for a + ?	on Apr 13
* Yes, I know that, but it is a question of consistency. Normal integers output a space.	rpgfan3233 on Apr 13
* PRINT also prints out a trailing space when numbers are printed	on Apr 15
*That explains why people add RTRIM$ as well as LTRIM$, even if STR$ removes it at the end	rpgfan3233 on Apr 15
* True, but STR$ can remove the RTRIM$ code also	on Apr 16
*Unsigned variables should be PRINTed with a leading space, I'll fix this.	on Apr 14
While your at it, perhaps a _TRIM function would be nice	on Apr 14
*It would be nice to have a built-in function rather than creating a QB TRIM function.	rpgfan3233 on Apr 14
There won't be an inbuilt TRIM function (to do LTRIM and RTRIM at once)...	on Apr 14
* Well I don't need a ROUND function either then thankyou	on Apr 15
*How were you planning on rounding a DOUBLE to a 64 BIT INTEGER then?	on Apr 15
* Can't you do DEF FN ROUND(X)=SGN(X)*INT(ABS(X)+0.5) ?	qbguy on Apr 15