Passing arrays to Subs.

[mjcoon]

Originally Posted by agraham

Calling without parentheses refers to Subs declared without a parameter list. I suspect you are trying to call a Sub that needs one or more parameters without the parentheses in which case the compiler will complain.

Hi Andrew, I assure you that your suspicions are unfounded. However further experimentation shows that my quote from the help apparently only applies to Subs that are declared without any return value typing. Since I like strong typing (I started with Algol-60 back in the 60s!) I like to use typing if the Sub is meant to return a value. Then I find that I have to put "()" in the declaration even if the Sub has no parameters.

This sort of stuff reminds me that although Algol-60 had just as much of a problem with defining the semantics as any other language, at least its syntax was tightly specified, so that syntactic units could be referred to unambiguously.

Regards, Mike.

[agraham]

Originally Posted by mjcoon

Since I like strong typing

So do I. One of the best things to happen to C was the introduction of strong typing in Borland and ANSI C - and it's one of the reasons I love .NET. But as Basic4ppc is untyped I don't understand what you mean at all - though I'm probably being stupid and missing the obvious.

I like to use typing if the Sub is meant to return a value. Then I find that I have to put "()" in the declaration even if the Sub has no parameters.

[mjcoon]

Originally Posted by agraham

... But as Basic4ppc is untyped I don't understand what you mean at all - though I'm probably being stupid and missing the obvious.

No, no, it's certainly not your stupidity, it's my inability to conform combined with Basic4ppc's acquiescence that caught me.

Following on from my use of Visual Basic at work, I had been declaring Subs with typing, and Basic4ppc had been indulging me, though perhaps just ignoring the types I specified. That was when I found that if I omitted the "()" to signify no parameter list that Basic4ppc started complaining.

In the interim I have now got my program working transferring binary data over serial RS232. So thank you very much for your work on sorting out the 0x1A problem, for providing SerialEx.dll and for your assistance to me. The BytesConverter.dll was crucial in interpreting the numerics embedded in the (Garmin GPS) binary stream, too.

Best wishes, Mike.