bug: maxit option in steady
Currently, the preprocessor assigns the maxit option for the steady command to options_.maxit_ and it is used in dynare_solve_block_bytecode.m for finding the steady state; dynare_solve.m, on the other hand, uses options_.solve_maxit (i.e. an option not passed to steady) for solve_algo = 1 or 2, whereas for solve_algo = 0 or 3 the values are hard-coded.
This needs to be made uniform. Stephane suggests assigning maxit to options_.solve_maxit in the preprocessor, changing dynare_solve_block_bytecode.m to use options_.solve_maxit, and replacing the hard-coded values in dynare_solve.m with this option as well.