Syntax error with if statement..

[Gary Miyakawa]

Ok, I've been writing this stuff for over a year and just bumped into this... I'm pretty sure it's something I'm doing wrong but I don't get it.. Someone please clue me in...

Here is the sample code that is cause me trouble.

'Activity module
Sub Process_Globals
End Sub
Sub Globals
   Dim f As Boolean
End Sub
Sub Activity_Create(FirstTime As Boolean)
   f = True
End Sub
Sub Activity_Resume
End Sub
Sub Activity_Pause (UserClosed As Boolean)
End Sub
Sub btnSettings
   If f = True
End Sub

When compiled, I get a "Syntax error (missing parameter)." on the If statement. "Word: true"...

Let me know where I'm wrong!

Thanks,

Gary M

 

[margret]

In your button event you had If with no Then. Not sure what you want the button event to do. Look below:

Sub btnSettings
   If f = True then
    End If
    'or
    f = True
End Sub

 

[Gary Miyakawa]

Thank you Margret... Just too close to the code... :signOops:

Gary M

 

[Penko]

Also, never forget to write True/False.

I mean, If(a = True) Then instead of if(a).
That's not so hard, but when it comes to:

if(str1.Contains("my substring"))

things really get complicating for me because it is the way I code in PHP for example!

 

[raytronixsystems]

I usually get all errors that are hard to identify when I forget the 'Then' keyword after an 'If' statement. I sometimes look for hours and wonder what went wrong then realize what I forgot. This is a very common mistake that probably all of us have encountered at one time or another. My background primarily in 'C/C++' and we didn't have the 'Then' construct. Maybe a future version of the B4a compiler could look for missing 'Then' and 'Endif' keywords and alert the user.

Best Wishes,
Ray

 

[MrRey]

As a fellow Ray, I know the feeling. I couldn't figure out why an ImageView wasn't showing. I later realized I had set Visible to false in Designer.

 

[Gary Miyakawa]

Good ideas folks ! and thanks for the support! Glad I'm not the only one that does this kind of stuff !

 

[ukimiku]

Me too. Before, I was working with a dialect of Basic that simply didn't require the THEN keyword:

if a = 3
   ... code to be executed iff a = 3
else
   ...
end if

I think the THEN is redundant, and should be made voluntary instead of obligatory in a future release of B4A. Like in a FOR... NEXT loop, the variable after the NEXT is not really necessary (and not even legal to supply in B4A). Out of habit, I sometimes forget to write THEN and, like you, wonder what may have caused this strange compilation problem.

Regards,