You know, I've used a number of languages (C, Pascal, SQL, etc.) that use the semicolon to separate commands, but I hardly ever used it to squeeze more code onto a single line. I just rarely find myself wishing this was possible outside of situations where it is:

If Foo Then Bar = 1Else Bar = 2

Where I did enjoy semicolons was in massive commands that spanned multiple lines (especially in SQL):

You can do this in RS (now Xojo), but have to use the underscore, and lose the ability to organize with tabs. But that's the whole point: If you don't know what you're looking for, a semicolon can be confusing, hard to find, and easy to forget. It also takes away from the simple, visual presentation of the editor. For my use, semicolons would have to be required and the whole auto-tabbing system removed. I'm happy with it as is.

Coming from anyone but you, I would have expected the responses to be 'This has been covered before', 'Real Basic/Studio/Xojo is not [other programming language]', etc.

Personally, I often prefer vertical space to jamming things into a single line, even when there are single line alternatives. Back in my VBA days, I would format my function calls with each parameter on a separate line for clarity. And, I never was a fan of Javascript's

Quote:

var x = (value=== "Green") ? "Go" : "Stop";

I'd rather use the following, as I find it easier to read:

Quote:

If (value == "Green") { x = "Go"} else { x = "Stop"}

But, it wouldn't matter to me if it was part of the language, I just wouln't use it much, if at all, myself. Just as long as we're not required to end each line that way (I have gotten in the habit of doing so in Javascript, but I often find myself missing a few every now and then.)

The semicolon trips me up, especially now that I'm doing more javascript/php. I keep trying to put a semicolon on RB code and leaving them off in php.

I hear you there! Between SQL, Pascal, and PHP, it can be a bit of a mental tongue-twister remembering the precise nuances of each syntax. Often I stare at the screen for a few blank moments, trying to summon up what I know that I knew.

The semicolon trips me up, especially now that I'm doing more javascript/php. I keep trying to put a semicolon on RB code and leaving them off in php.

I hear you there! Between SQL, Pascal, and PHP, it can be a bit of a mental tongue-twister remembering the precise nuances of each syntax. Often I stare at the screen for a few blank moments, trying to summon up what I know that I knew.

What I sometimes do in my PHP work is first figure out what I need (duh) then write working code in RB, then convert it to PHP.

Since I'm still new to PHP this reduces the learning curve and lookup time for me