Bug? Complete keyword

Alessandro71 said:

By pure chance I've found a line in my code that wasn't marked as as syntax error and compiles fine:

B4X:

Wait For (sf) Completa (Result As Int)
'Completa instead of Complete

Click to expand...

LucaMs said:

Are you sure?

View attachment 122349

Click to expand...

    Dim sf As Object = B4XPages.MainPage.Msg.ShowMsgbox2Async("Are you sure you want to restart?", "Warning", "Yes", "", "No")
    Wait For (sf) Completa (Result As Int)

Public Sub ShowMsgbox2Async(message As Object, title As Object, positive As String, cancel As String, negative As String) As ResumableSub
    Dim msg As String = message
    WriteLog(msg.Replace(CRLF, "|"))
    
    Dim sf As Object
    sf = xui.Msgbox2Async(message, title, positive, cancel, negative, Null)
    Wait For (sf) Msgbox_Result (Result As Int)

    Select Result
        Case xui.DialogResponse_Positive
            WriteLog("user answer positive")
        Case xui.DialogResponse_Negative
            WriteLog("user answer negative")
        Case xui.DialogResponse_Cancel
            WriteLog("user answer cancel")
        Case Else
            WriteLog("Unknown user answer")
    End Select
    
    Return Result
End Sub

agraham said:

I see this if there is

Dim sf As Object = xxxx
Wait For (sf) Complet(res As Object)

The checkhere seems to be for 'Complet' and not 'Complete'. I guess there is a separate block of IDE code that parses Wait For an Object rather than Wait For a Sub call.

Click to expand...

LucaMs said:

But I also wrote CompletA, as

Click to expand...

agraham said:

I know, the match stops at 'Complet' so 'Complata' through to 'Completx' match as does 'Completanything'!

Click to expand...

LucaMs said:

, not for me!

Click to expand...

agraham said:

I think you are waiting on a Sub call 'Pippo' (I assume it's a Sub) and not an Object like his and my examples.

Click to expand...

Erel said:

This is not a bug.
The only case where the compiler will raise an error is when you call a resumable sub.
In other cases the compiler cannot know the correct event name.

B4X:

Wait For (MyResumableSub) Completa (x As Y) 'error here
Wait For (AnythingElse) Completa (x As Z) 'this is valid

Click to expand...

LucaMs said:

The event that Wait For awaits is the first name (AnythingElse, in the example), isn't it?

Click to expand...

LucaMs said:

The event that Wait For awaits is the first name (AnythingElse, in the example), isn't it?

Click to expand...

Erel said:

No. This is the "sender filter" object.

Click to expand...

Sub AppStart (Form1 As Form, Args() As String)
    MainForm = Form1
    MainForm.RootPane.LoadLayout("Layout1")
    MainForm.Show
   
    Wait For TaskCompleted(Result As String)
    Log(Result)
End Sub

Sub Button1_Click
    ' If I used CallSub2 instead of CallSubDelayed2, the project would crash.
    ' Why? <---
    CallSubDelayed2(Me, "TaskCompleted", "Done")
End Sub

LucaMs said:

[Disregard the fact that the following example looks stupid; it's part of an old question]

Click to expand...

Erel said:

it is recommended to use CallSubDelayed to raise events that are expected to be caught with Wait For.

Click to expand...

LucaMs said:

The event that Wait For awaits is the first name (AnythingElse, in the example), isn't it?

Click to expand...

Erel said:

In other cases the compiler cannot know the correct event name.

Click to expand...

Erel said:

This is not a bug.
The only case where the compiler will raise an error is when you call a resumable sub.
In other cases the compiler cannot know the correct event name.

B4X:

Wait For (MyResumableSub) Completa (x As Y) 'error here
Wait For (AnythingElse) Completa (x As Z) 'this is valid

Click to expand...