Accelerometer | ADC | ADXL | Adxl20 | AVR | BasicStamp | BX-35 | BX28 | BX35 | COM3 | Compiler | Downloader | EEPROM | Electromagnet | GetADC | GP2D1 | GPS | I2C | IDE | Keypad | LCD | LCD+ | MIDI | Motors | Multitasking | Netmedia | Networking | PCB | PID | PlaySound | PWM | Relays | RTC | Servo | ShiftOut | SitePlayer | SPI | Stack | Timer | USB

Why does the following procedure produce a syntax error? Any idea
anyone. Thank-you for your time!

Option Explicit

Dim OutputBuffer(1 To 30) As Byte
Dim InputBuffer(1 To 13) As Byte

Public CreateFile(ByVal FileName As String)

Call Delay(0.5) <-------------------- Syntax Error (?...)

Call OpenQueue(OutputBuffer, 30)
Call OpenQueue(InputBuffer, 13)

Call DefineCom3(6,5,bx0000_1000)
Call OpenCom(3, 9600, InputBuffer, OutputBuffer)

Call PutQueueStr(OutputBuffer, FileName)
Call PutQueueStr(OutputBuffer, chr(13) & chr(10))

End Sub



(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

> Public CreateFile(ByVal FileName As String)
>
> Call Delay(0.5) <-------------------- Syntax Error (?...)

I think your error is in the previous line, which should be Public Sub
CreateFile [...]. I think you defined a string named CreateFile, but
that syntax would be odd, too.
Tom



(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

morenovrichard wrote:

Public _*Sub*_ CreateFile(ByVal FileName As String)

[Non-text portions of this message have been removed]


(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

You have several mistakes:

Most important, your program needs a Main procedure. Add the lines:

Public Sub Main()
Call CreateFile( << File Name here >> )
End Sub

Also, you need the word "Sub" in your procedure declaration:

Public Sub CreateFile(ByVal FileName As String)

NOT: Public CreateFile(ByVal FileName As String)

If you have a copy of my book, I discuss procedures and functions in
Chapter 12.

chris

--- In b...@yahoogroups.com, "morenovrichard"
wrote:
>
> Why does the following procedure produce a syntax error? Any idea
> anyone. Thank-you for your time!
>
> Option Explicit
>
> Dim OutputBuffer(1 To 30) As Byte
> Dim InputBuffer(1 To 13) As Byte
>
> Public CreateFile(ByVal FileName As String)
>
> Call Delay(0.5) <-------------------- Syntax Error (?...)
>
> Call OpenQueue(OutputBuffer, 30)
> Call OpenQueue(InputBuffer, 13)
>
> Call DefineCom3(6,5,bx0000_1000)
> Call OpenCom(3, 9600, InputBuffer, OutputBuffer)
>
> Call PutQueueStr(OutputBuffer, FileName)
> Call PutQueueStr(OutputBuffer, chr(13) & chr(10))
>
> End Sub
>



(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

This looks like a bug in the compiler. This same code in the Main sub
compiles fine:

Option Explicit
Dim OutputBuffer(1 To 30) As Byte
Dim InputBuffer(1 To 13) As Byte
Dim FileName As String

Public Sub Main()

Call Delay(0.5)

Call OpenQueue(OutputBuffer, 30)
Call OpenQueue(InputBuffer, 13)

Call DefineCom3(6,5,bx0000_1000)
Call OpenCom(3, 9600, InputBuffer, OutputBuffer)

Call PutQueueStr(OutputBuffer, FileName)
Call PutQueueStr(OutputBuffer, chr(13) & chr(10))
End Sub
Go figure...


(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

--- In b...@yahoogroups.com, "benoit_bleau1" wrote:
>
> This looks like a bug in the compiler. This same code in the Main sub

Darn.... I missed the *SUB*... egg on my face

-Ben


(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

> Darn.... I missed the *SUB*... egg on my face
It's a common mistake to leave out or mispell something like that.
For future reference, when the compiler complains about a line of code
that looks correct, comment out that line, and recompile it. Often,
the compiler will narrow down the problem a bit more for you. Also,
try not to concentrate too much on the line that the compiler thinks
is the problem (obviously after you have verified that the line in
question is correct). Look at the preceding and following code for
mistakes as well.

As a side note, there have been compiler bugs in the past that could
cause the compile to fail if there were spaces or other invisible
characters at the end of the line. I don't recall if this has
happened with the BasicX compiler, but it has been known to happen
nonetheless. The fix was usually to simply delete the line and retype
it. Cutting and pasting just pastes the bad characters again, so
retyping is necessary.

Just my $0.02

-Don


(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )