Error Parsing "If"

[Charles Pegge]

Option 2 would be consistent with a colon always being interpreted as a soft line break.

2  if a=1 : b=1 : end if   'endif explicit

That leaves case as the slightly odd one out.

case a : b=1

[Mike Lobanovsky]

No oddity seen here, Charles. The case that follows marks unambiguously the end of case immediately preceding it while end select will mark the end of entire block.

[Mike Lobanovsky]

I don't know is there a way to replace UDT variables with ordinary typed...maybe   

Absolutely no problem here, Aurel. Just split each UDT into two simple variables and create two arrays for them. The array sizes will be the same and the indices within them will point to the same elements that they pointed to when each two-member UDT was still a single entity. This would be the easiest problem throughout the entire port.

but this is standard tactic anyway...

But it shouldn't be, at least as far as standard language constructs are concerned. This is why I'm so agitated: Charles is shaking the foundations and I'm already seeing the first bricks fall off the roof and bump on my head.

[Charles Pegge]

I think option 2 tips the balance in your favour, Mike:

We can now do expressions like this (if we really want to):

sys a=2, b=0

if a=1 : b=1 : elseif a=2 : b=2 else b=3 : end if

or

if a=1 then : b=1 : elseif a=2 then : b=2 : else : b=3 : end if

print b

[Mike Lobanovsky]

Are you sure there are no typos here?

sys a=2, b=0
if a=1 : b=1 : elseif a=2 : b=2 else b=3 : end if
print b

And I suppose there may be anything instead of a sys here? (Just asking to be on the safe side, hehe...)

A voice in the wilderness again... yet maybe this is somehow better than nothing at all.

[Charles Pegge]

Yes, Any primitive type: int, float or string.

I'm testing as we 'speak'. It works any which way. keywords then / else / elseif : are all expression terminators.

[Mike Lobanovsky]

It works any which way. keywords then / else / elseif : are all expression terminators.

Does that mean :'s after then and before else and elseif (and I suppose, before end too) are optional???

[Charles Pegge]

The colon after then is essential to distinguish it from lines like

if a>1 then b=1


Similarly, a colon must come after an elseif condition.

end if / endif must be preceded by a colon under current parsing rules.

then is optional in these cases

[JRS]

This is why I'm glad Peter Verhas made the wise decision to only allow one statement per line.

This is a legal variable name in SB.

Hi = Hello:World

[Mike Lobanovsky]

Charles,

Is your

b=2 else b=3

correct?


Hi John,

one statement per line

No "soft" line breaks (like : here) at all?

[JRS]

Code: [Select]

PRINT test( _
arg1, _
arg2, _
"""
               Multi
               Line
               String
""")

This is one statement.

[Mike Lobanovsky]

This is one statement.

Got it. The only legit line break is a *nix LF (0xA).

BTW FBSL's multiline string would be

"
Multi
Line
String
"

to be printed as

Multi
Line
String

Yours would be printed to the console as

"
Multi
Line
String
"



Charles,

What about my last question, please?

[Charles Pegge]

Yes Mike, the else syntax works the same as before. I am almost ready to post an update. Just working through the permutations.

if a=1 then b=1 else b=5

[JRS]

a = _
"""
"Multi",
"Line',
'String'
"""
 

[Mike Lobanovsky]

Charles,

Please "yes" or "no":

if a=1 : b=1 : elseif a=2 : b=2 else b=3 : end if

does not require a colon before else, does it?