Programming errors on QB64

[kservice]

Tell me, please, what is the error? 
 [ You are not allowed to view this attachment ]  
Error in line 124

[Petr]

In your source code is not SUB named as zaglavie:

here is your source code
...
..
..
..
..

here is your SUBs and FUNCTIONs

SUB zaglavie
...
... next source code in this SUB
...
END SUB

[FellippeHeitor]

You didn't separate the Call from the comment:

Code: QB64: [Select]

1. Call zaglavie1(): rem ...

Notice:
1- Call is optional:

Code: QB64: [Select]

1.  zaglavie1: rem ...

2- rem is optional, if you use the apostrophe - and if you don't use rem, you don't have to separate the comment from the main line with a colon:

Code: QB64: [Select]

1. zaglavie1 'some comment

[Petr]

Here is example:
@FellippeHeitor  it works also without : separator with REM :)

Code: QB64: [Select]

1. DO
2.     CLS
3.     CALL ShowTime REM here is something wrong!
4.     _DISPLAY
5.     _LIMIT 20
6. LOOP
7.  
8. SUB ShowTime
9.     LOCATE 1
10.     PRINT TIME$
11. END SUB
12.  
13.  
14.  

[Petr]

@kservice

Next option is, if zagalvie1 SUB exists in your source code, remove brackets from CALL statement.

[kservice]

In your source code is not SUB named as zaglavie:

All called functions are in a separate file.
  [ You are not allowed to view this attachment ]  

After separating the function of the function and the comment has not changed
  [ You are not allowed to view this attachment ]  

[Petr]

So zaglavie1 is not SUB, because if is, then you must have this error message:

(SUB must be included at the end the source code)

  [ You are not allowed to view this attachment ]  

[SMcNeill]

Can you call a sub with blank parameters?  If it’s blank, shouldn’t it just be omitted?

CALL X()

SUB X
  PRINT “foo”
END

[TempodiBasic]

Hi
Fine behaviour...

Code: QB64: [Select]

1. Cls
2. Print "1"
3. Call print2 Rem ' it is a modern comment
4. Print 3
5. print2 Rem it is a classical comment
6. End
7.  
8. Sub print2 ()
9.     Print "Hi I'm SUB print2 and I do this...";
10.     Print 2
11. End Sub

  [ You are not allowed to view this attachment ]  
yes I can confirm that the error is NOT related to the absence of : between  print2 and Rem
moreover also if I type : the error stays there.
If I erase the () all become ok.

Are there some differences with QB45?  I dunno.

[SMcNeill]

It’s the blank parameters.

Call x()

Sub x()
   PRINT “foo”
End Sub

  [ You are not allowed to view this attachment ]  

[TempodiBasic]

Yes trying the same code in QBasic
this last warns the user to put arguments between ( )
Moreover it doesn't tolerate a REM without a : before it!

[FellippeHeitor]

Yeah, today I learned QB64 doesn't mind if there's a colon before a REM comment.

It's only mandatory in DATA lines.

[kservice]

Thanks to all for participation and advice. The program is large, many different functions that I combined into the plug-in file.
       Advise how to better make functions from this file? Can there be 2-3 connected files?
The program was created for many years ago for QB45 and now, when there is free time, trying to transfer to QB64. On QB45 everything worked. Here, apparently, checking over compiling more careful.
I'm trying to figure it out. So far not everything turns out. So I take a break. I am free from other cases - I will continue.
   Checked such a test variant - works without errors
  [ You are not allowed to view this attachment ]  

[kservice]

In the  QB45 program i am used the FRE(-1) command. In QB64, this keyword is not supported. Something can be replaced?
Or here it is not necessary?

     And another question. I repeatedly use the functions of the form
Sub Chtenie1 (SKLSUM#, U$, f$, NB$, NE$, DT$, FRM$, RR, C, PP, tov() As Tovar).
Variable tov () AS Tovar is read from the f$ file. This is an array, in each row of which 4 pemet. But at the same time an
"IncorRect Array Type Passed to Sub" error occurs.
     How can this problem be solved?

[FellippeHeitor]

There's no direct equivalent to FRE() in QB64. You will have to query the operating system (research the API) to check how much free memory is available.

Unless your program relied directly on knowing how much free memory there was, you can probably safely remove the FRE() occurrences.