Displaying 3 results from an estimated 3 matches for "lbuffer".
Did you mean:
buffer
2000 Oct 03
0
FW: Parse Errors
...Baier's function R_Proxy_evaluate
contained in proxy_impl.c -- when I issue an invalid command to R such as
"plo(x)" the program crashes. There is code in R_Proxy_evaluate to test for
a parse error before actually generating code and issuing the command - He
calls R_Parse1Buffer(&lBuffer,0,&lStatus) and then tests the value of
lStatus for parse error. The trouble is that lStatus == PARSE_OK even though
the command is invalid, so the evaluation continues until eval() is called,
at which point R terminates and crashes the program. (It does write an
error message to the console f...
2000 Oct 03
2
Parse Errors
...Baier's function R_Proxy_evaluate
contained in proxy_impl.c -- when I issue an invalid command to R such as
"plo(x)" the program crashes. There is code in R_Proxy_evaluate to test for
a parse error before actually generating code and issuing the command - He
calls R_Parse1Buffer(&lBuffer,0,&lStatus) and then tests the value of
lStatus for parse error. The trouble is that lStatus == PARSE_OK even though
the command is invalid, so the evaluation continues until eval() is called,
at which point R terminates and crashes the program. (It does write an
error message to the console f...
2000 Oct 03
2
Parse Errors
...Baier's function R_Proxy_evaluate
contained in proxy_impl.c -- when I issue an invalid command to R such as
"plo(x)" the program crashes. There is code in R_Proxy_evaluate to test for
a parse error before actually generating code and issuing the command - He
calls R_Parse1Buffer(&lBuffer,0,&lStatus) and then tests the value of
lStatus for parse error. The trouble is that lStatus == PARSE_OK even though
the command is invalid, so the evaluation continues until eval() is called,
at which point R terminates and crashes the program. (It does write an
error message to the console f...