QB64 NOT RELIABLE FOR LARRY

[RhoSigma]

Sometimes it's just funny how people get wrong even the simpliest hints. Of course the ## have to be in quotes just like you did the # in quotes in your first example ;-)

And just to mention, if your numbers get bigger you may need 3,4,5 of the #. Each # represents 1 digit of a number.

[SMcNeill]

You forgot your quotes.

PRINT USING “##”; a ^ 2

[Kernelpanic]

You forgot your quotes.

PRINT USING “##”; a ^ 2

No! That is not the problem. I think not.

[doppler]

The troll larry made one post and got a response.

[SMcNeill]

No! That is not the problem. I think not.

Two points here:

POINT 1) You have to use enough ###### symbols to represent a placeholder for your result.

USING “#” reserves 1 digit.
USING “##” reserves 2 digits.
USING “###” reserves 3 digits.

POINT 2) The negative sign counts as 1 digit.

1 is 1 digit.
-1 is 2 digits.
12 is 2 digits
-12 is 3 digits.

If the number you are trying to display has more digits that you reserved, the % symbol will print in front, representing, “The programmer who wrote this was an idiot and didn’t reserve proper space for formatting.  Tell them to fix it!”

Reserve enough digits and you’ll never see that error symbol again.

[Petr]

LARRY wrote:

First, I had problems with a quote left in an alpha field. Next, it was problems with negative numbers.  Some programs were running quite well but failed upon making changes and recompiling.

This version of QB is NOT worth using.  I have never seen such a buggy language.  I have worked as a programmer on main frames for 40+ years.

How much time did you give it? And how many times have you tried to correct mistakes? And what exactly are you talking about? :)
The problem will definitely be between the chair and the keyboard.

[bplus]

Where? Here not:

Positive numbers are always 1 space more that what you see, check the LEN:

Code: QB64: [Select]

1. a = -5
2. PRINT LEN(STR$((a) ^ 2))
3.  

Opps wrong page! :P already noted on 2nd page.

[Kernelpanic]

If the number you are trying to display has more digits that you reserved, the % symbol will print in front, representing, “The programmer who wrote this was an idiot and didn’t reserve proper space for formatting.  Tell them to fix it!”

Well, do it!

I wrote it: No more "###" and so on. I know this! The problem is, the input decides the output. I do not know the input.

PS: Maybe I have an idea, but not now. In Berlin is it 00:05 - Good Night!

Code: QB64: [Select]

1. DIM a AS INTEGER, b AS INTEGER
2.  
3. a = -5
4. b = 6
5.  
6. PRINT USING "##"; a ^ 3
7. PRINT
8.  
9. PRINT USING "The Number: ####### is wrong!"; b ^ 3
10. PRINT
11. PRINT USING "The Number: ### is wrong!"; b ^ 3
12. PRINT
13.  
14. INPUT "Enter a number: ", b
15. PRINT USING "The Number: ####### is wrong!"; b ^ 3
16. PRINT
17. PRINT USING "The Number: ### is wrong!"; b ^ 3
18. PRINT
19.  
20.  
21. PRINT (a) ^ 2
22. PRINT
23. PRINT -3 ^ 2
24. PRINT
25. PRINT (-3) ^ 2
26.  
27. PRINT
28. 'Unexpected character . . .
29. 'PRINT LEN ( STR $ ( ( a ) ^ 2 ) )
30.  
31. END
32.  

[bplus]

Yeah this is crazy but works:

Code: QB64: [Select]

1. INPUT "Integer please ", a&
2. s$ = STRING$(LEN(STR$(a&)), "#")
3. PRINT "The number input was";
4. IF a& < 0 THEN PRINT " ";
5. PRINT USING s$ + "."; a&
6.  

[SMcNeill]

Well, do it!

I wrote it: No more "###" and so on. I know this! The problem is, the input decides the output. I do not know the input.

https://www.qb64.org/wiki/Data_types

As a programmer, you're going to know what the maximum value is that an user can input -- you define it with your variable type.

If you use _BYTE for your variable types, you reserve a maximum of 4 spaces (-128 to 127).
If you use INTEGER for your variable types, you reserve a maximum of 6 spaces (-32768 to 32767).
If you use LONG for your variable types, you reserve a maximum of 11 spaces.
If you use _INTEGER64 for your variable types, you reserve a maximum of 20 spaces.

The point of PRINT USING is to create a form which will line up and keep all your data in a nice neat row.  To do that, you have to allocate space for the largest result, and not dynamically adjust your fields on the fly.

If all you want is to do something like bplus has done above, then don't even use PRINT USING at all.  Just print the answer as it exists.

Code: QB64: [Select]

1. INPUT "Integer please ", a&
2. PRINT "The number input was"; a&
3.  

As per your examples above:

Code: [Select]

DIM a AS INTEGER, b AS INTEGER

a = -5
b = 6

PRINT a ^ 3
PRINT

PRINT "The Number:"; b ^ 3; "is right!"
PRINT
PRINT "The Number:"; b ^ 3; "is right!"
PRINT

INPUT "Enter a number: ", b
PRINT "The Number:"; b ^ 3; "is right!"
PRINT
PRINT "The Number:"; b ^ 3; "is right!"
PRINT


PRINT (a) ^ 2
PRINT
PRINT -3 ^ 2
PRINT
PRINT (-3) ^ 2

PRINT
END


 
What's the obsession with USING?  For what it seems you want to do, it's not needed at all.  Just print the dang value to the screen and be done with it.

[Kernelpanic]

This is my idea for a correct formatting. But there is a problem: with sums of 100,000.00 or more, "%" is prefixed, regardless of whether "#" x 6,7,9, the character does not go away. I do not find the fault.

The 2nd program is only an example, there the formatting works as it should be.

Kredithoehe/Kredit = Loan amount
Rückzahlungsbetrag = Repayment amount

Code: QB64: [Select]

1. OPTION _EXPLICIT
2.  
3. DECLARE FUNCTION Rueckzahlung# (Kredit as Double)
4.  
5. DIM Kredithoehe AS DOUBLE
6.  
7. PRINT
8. INPUT "Gewuenschte Kredithoehe eingeben: ", Kredithoehe
9. SELECT CASE Kredithoehe
10.   CASE IS <= 999.99
11.     PRINT USING "Rueckzahlungsbetrag: ####,.## Euro"; Rueckzahlung#(Kredithoehe)
12.   CASE IS >= 1000.00
13.     PRINT USING "Rueckzahlungsbetrag: #####,.## Euro"; Rueckzahlung#(Kredithoehe)
14.   CASE IS >= 10000.00
15.     PRINT USING "Rueckzahlungsbetrag: ######,.## Euro"; Rueckzahlung#(Kredithoehe)
16.   CASE IS >= 100000.00
17.     PRINT USING "Rueckzahlungsbetrag: #######,.## Euro"; Rueckzahlung#(Kredithoehe)
18.   CASE IS >= 1000000.00
19.     PRINT USING "Rueckzahlungsbetrag: ########,.## Euro"; Rueckzahlung#(Kredithoehe)
20.   CASE ELSE
21.     PRINT: PRINT "Falsche Eingabe!"
22. END SELECT
23.  
24. END '(Hauptprogramm)
25.  
26. FUNCTION Rueckzahlung# (Kredit AS DOUBLE)
27.   Rueckzahlung# = ((Kredit / 10) + Kredit)
28. END FUNCTION
29.  

---

Code: QB64: [Select]

1. OPTION _EXPLICIT
2.  
3. DECLARE FUNCTION# (Kredit as double)
4.  
5. DIM Sum AS DOUBLE, Sum2 AS DOUBLE
6.  
7. Sum = 150000.00
8.  
9. INPUT "Summe -Max 6 Stellen- : ", Sum2
10. PRINT USING "######,.##"; Sum
11. PRINT
12. PRINT USING "Eingabe ist: ######,.##"; Sum2
13. PRINT
14. 'Examole for wrong format
15. PRINT USING "Falsche Formatierung: ###,.##"; Sum2
16. PRINT
17. PRINT USING "Summe mit Zinsen: ######,.##"; Rueckzahlung(Sum2)
18.  
19. END
20.  
21. FUNCTION Rueckzahlung# (Kredit AS DOUBLE)
22.   Rueckzahlung# = ((Kredit / 10) + Kredit)
23. END FUNCTION
24.  

[Cobalt]

lets start a new topic for pertinent stuff and let this idiot topic fall into the seclusion of darkness it deserves.

[SMcNeill]

Code: QB64: [Select]

1. OPTION _EXPLICIT
2.  
3. DECLARE FUNCTION Rueckzahlung# (Kredit AS DOUBLE)
4.  
5. DIM Kredithoehe AS DOUBLE
6.  
7. PRINT
8. INPUT "Gewuenschte Kredithoehe eingeben: ", Kredithoehe
9. SELECT CASE Kredithoehe
10.     CASE 0 TO 999.99
11.         PRINT USING "Rueckzahlungsbetrag: ####,.## Euro"; Rueckzahlung#(Kredithoehe)
12.     CASE 1000.00 TO 9999.99
13.         PRINT USING "Rueckzahlungsbetrag: #####,.## Euro"; Rueckzahlung#(Kredithoehe)
14.     CASE 10000.00 TO 99999.99
15.         PRINT USING "Rueckzahlungsbetrag: ######,.## Euro"; Rueckzahlung#(Kredithoehe)
16.     CASE 100000.00 TO 999999.99
17.         PRINT USING "Rueckzahlungsbetrag: #######,.## Euro"; Rueckzahlung#(Kredithoehe)
18.     CASE IS >= 1000000.00
19.         PRINT USING "Rueckzahlungsbetrag: ########,.## Euro"; Rueckzahlung#(Kredithoehe)
20.     CASE ELSE
21.         PRINT: PRINT "Falsche Eingabe!"
22. END SELECT
23.  
24. END '(Hauptprogramm)
25.  
26. FUNCTION Rueckzahlung# (Kredit AS DOUBLE)
27.     Rueckzahlung# = ((Kredit / 10) + Kredit)
28. END FUNCTION
29.  
30.  

The problem with your code, as you presented it, is that 100,000 is also greater than 10,000.  Since the SELECT CASE > 10,000, it gets processed as a 5 digit value, and not a 6 digit one.  Solution is to simply define the ranges, as I've done above, so that the proper SELECT CASE is triggered.

Even simpler:  Just build the string to whatever size you need it.

Code: QB64: [Select]

1. OPTION _EXPLICIT
2.  
3. DECLARE FUNCTION Rueckzahlung# (Kredit AS DOUBLE)
4.  
5. DIM Kredithoehe AS DOUBLE, length AS INTEGER, use AS STRING
6.  
7. PRINT
8. INPUT "Gewuenschte Kredithoehe eingeben: ", Kredithoehe
9.  
10. length = LEN(STR$(INT(Rueckzahlung#(Kredithoehe)))) 'get the length
11. use$ = "Rueckzahlungsbetrag: " + STRING$(length, "#") + ",.## Euro" 'use that length to create the proper number of # symbols
12. PRINT USING use$; Rueckzahlung#(Kredithoehe) 'print using the created string
13.  
14. END '(Hauptprogramm)
15.  
16. FUNCTION Rueckzahlung# (Kredit AS DOUBLE)
17.     Rueckzahlung# = ((Kredit / 10) + Kredit)
18. END FUNCTION

[Kernelpanic]

@SMcNeill - That was it! Thank You!

That with "build a string" I still have to look closely.

[Kernelpanic]

Ok, the String variant is better. More practicable, really. Thanks!