There is a flag in the RobotC Compiler that is normally set that allows the use of parenthesis in place of a brackets. I turned it off when I noticed that I had a syntax error in my code and it was not flagged. When I turned it off, it flagged my error and another in the third party driver "lego-touch.h". I did not test any other drivers but I do also use IRSeeker, Sonar, lights and no errors were flagged in those drivers.

I started a support ticket ([#437747] Syntax error not flagged) and they suggested I let Xander know. So here it is.

Here are the errors reported for lego-touch.h:

Line 1 bool TSreadState(tSensors link) {
Line 2 if ((SensorType(link) != sensorTouch) && SensorMode(link) != modeBoolean) {
Line 3 SetSensorType(link, sensorTouch);
Line 4 SetSensorMode(link, modeBoolean);

Line 1: N
Line 2 Errors:
**Error**:Variable 'SensorType' is not a Procedure.
**Error**:Too many parameters specified. Call to 'SensorType'. Parameter: 'N/A' is 'link' of type 'tSensors'.
**Error**:Variable 'SensorMode' is not a Procedure.
**Error**:Too many parameters specified. Call to 'SensorMode'. Parameter: 'N/A' is 'link' of type 'tSensors'.
Line 3 Errors:
**Error**:Internal Compiler: Unexpected use of proc 'SensorType' in an expression
**Error**:LValue for '[]' operator must be a pointer
**Error**:'[]' operator requires pointer value on left hand side [2].
Line 4 Errors:
**Error**:Internal Compiler: Unexpected use of proc 'SensorMode' in an expression
**Error**:LValue for '[]' operator must be a pointer
**Error**:'[]' operator requires pointer value on left hand side [2].

Hi there,

SensorType is an array, not a function. Simply replace all instances of SensorType(...) with SensorType[...]. Same applies to SensorMode.

Let me know if that fixes it.

Regards,
Xander

I changed line 2 of my message below to: if ((SensorType[link] != sensorTouch) && SensorMode[link] != modeBoolean) {

in lego-touch.h and the errors are no longer flagged. Will you be making those changes in your next release? Perhaps testing without that flag set in the compiler might be in order.

Thanks, Mentor 3923 FTC

I had no idea that flag even existed, much less was enabled.

Thanks for reporting the bug.

= Xander