Curious if I am thinking about this right.

[bplus]

Two!

Code: (Select All)

Input "Enter a Number to convert , (comma) 1 to convert to mm from inches or ,(comma) any other for inches "; num, op%

Print _IIf(op% = 1, num * 25.4, num / 25.4) ' 25.4 mm per inch

This takes advantage of being able to assign multiple input values to variables.

---

"I'm lazy. I like to program in a manner that supports me being as lazy as possible. Big Grin"

I am that way with typing, unfortunately NOT with Editing!

Yeah 2 liner to show both conversions good too! Saves on variables +1

[SMcNeill]

Two!

Code: (Select All)

Input "Enter a Number to convert , (comma) 1 to convert to mm from inches or ,(comma) any other for inches "; num, op%

Print _IIf(op% = 1, num * 25.4, num / 25.4) ' 25.4 mm per inch

This takes advantage of being able to assign multiple input values to variables.

You're going in the wrong direction here.  The usage is getting more obtuse and harder to decipher; not easier.  Keep it simple and easy to understand and use.  Lines of code don't matter for squat if you can't use the end product easily.

[bplus]

Yeah better!

Code: (Select All)

Input "Enter a Number to convert inches to mm and vice versa"; num

Print num * 25.4; "mm", num / 25.4; "inches"

Why choose get 'em BOTH! Be generous

[SMcNeill]

Yeah better!

Code: (Select All)

Input "Enter a Number to convert inches to mm and vice versa"; num

Print num * 25.4; "mm", num / 25.4; "inches"

That's basically what I did on the other page, except I used to PRINT USING to make certain that I didn't end up with some crazy scientific notation values for my numbers.  1 mm = 6.12345678981264827556tF+3 or such.  LOL!   

[bplus]

Is two lines small enough? No?

Code: (Select All)

Print Val(_InputBox$("Convert number from inches to mm.", "Enter a number")) * 25.4

[SMcNeill]

Is two lines small enough? No?

Code: (Select All)

Print Val(_InputBox$("Convert number from inches to mm.", "Enter a number")) * 25.4

Half the number of lines, with less than half the functionality.  You're moving in the wrong direction again here.

What is with the obsession to try and produce the fewest possible number of lines of code for a program?   Whatever happened to readability and functionality?  Particularly when offering demos for a new user?

[SMcNeill]

Here -- one line, 29 characters:

Code: (Select All)

Input n:?n*25.4"mm"n/25.4"in"

[Dimster]

What a great question that turned out to be Protocog . Like dueling banjos, the music was awesome. There are some awfully clever codes on this site.

[bplus]

the dueling continues

"Wrong direction" ??? me with a true one-liner single statement showing another feature of QB64pe that can not be found in that other vesion of QB64.
Low bytes is good too, for sure!, but that is another direction ("colonscopey" let's call it) which I don't dare call "wrong", just a little misguided maybe.

let me quote some guy I know and love:
"Particularly when offering demos for a new user?"

yeah Mark try to have the last word with that guy!

@Dimster what do you mean WAS awesome?

[bplus]

"Oh you speed demo" ah, Charlie I had so much less typing to do

That is freak'n interesting code you had back there @CharlieJV
https://qb64phoenix.com/forum/showthread...6#pid31416

I see your Input can take variable string for/in the prompt And something funny about IF THEN Structure there too.
I must warn newbies that this BAM code is NOT QB64pe code but a very close cousin.