After making a run over Marias Pass 3.1 I checked the log file for warnings. Most were minor and easily fixed. I have about a dozen warnings of the 2 lines below with different line numbers:
CARSPAWN SIGSCR
Warning: sigscr-file line 64 : Unexpected number of ( in function call : DEBUG_OUT (BLOCK_STATE(
Warning: sigscr-file line 65 : Unexpected number of ( in function call : DEBUG_OUT (ROUTE_SET(
if (has_USER4)
{
debug_header();
debug_out (100);
debug_out (enabled);
debug_out (block_state()); <<<<<<<<<<<<<< LINE 64
debug_out (route_set()); <<<<<<<<<<<<<< LINE 65
debug_out (next_state);
debug_out (next_state_mr);
debug_out (opp_state);
}
I removed the extra set of brackets and OR seems happy since the warnings no longer appear. In MSTS the signals appear to operate ok but I know nothing about the inner workings of them. Is there any way to test them to make sure I didn't solve a problem in OR and create one in MSTS?
Rich
CARSPAWN SIGSCR
Warning: sigscr-file line 64 : Unexpected number of ( in function call : DEBUG_OUT (BLOCK_STATE(
Warning: sigscr-file line 65 : Unexpected number of ( in function call : DEBUG_OUT (ROUTE_SET(
if (has_USER4)
{
debug_header();
debug_out (100);
debug_out (enabled);
debug_out (block_state()); <<<<<<<<<<<<<< LINE 64
debug_out (route_set()); <<<<<<<<<<<<<< LINE 65
debug_out (next_state);
debug_out (next_state_mr);
debug_out (opp_state);
}
I removed the extra set of brackets and OR seems happy since the warnings no longer appear. In MSTS the signals appear to operate ok but I know nothing about the inner workings of them. Is there any way to test them to make sure I didn't solve a problem in OR and create one in MSTS?
Rich



Comment