Re: User input combined, error "input: reading user-input failed!"

[hkhauke]

Hi again,

I found out a little more details about the unexpected error as described in
my previous mail:

It is not the mexPrintf command that causes the problem. Instead, I have
identified that it is a 
call to my own parser function "yyparse();" in the C-code of the Mex file
which is based on 
the flex and bison tools.

If I put this command (yyparse()) into comments in my mex-file C-Code, the
Octave interpreter 
stops on the "input('...','s');" command in the Matlab code after the Mex
file is called.
Then, I can specify my selection. 

If I DO NOT put "yyparse();" in comments, the "input('..', 's');" line is
ignored for the first time and it 
leads to the error message "input: reading user-input failed!" for the
second time the "input('..', 's')"
command is used.

My guess is: The Octave interpreter also uses flex and bison somehow, and
since it is C with global
variables, I corrupt these variables by writing to what I expected to be my
own private variables.

Anybody got more details on the parsing procedure in Octave?

Thank you for any help and Merry Christmas

Hauke 



--
View this message in context: 
http://octave.1599824.n4.nabble.com/User-input-combined-error-input-reading-user-input-failed-tp4648378p4648391.html
Sent from the Octave - General mailing list archive at Nabble.com.