Quote:> 1) I would like to increase the maximum command buffer length for the serial
> terminal. It is currently limited to 128 characters. I cannot find a #define
> for that value.
No, you can't change this value without recompiling the shell. You
will need to ask Wind River for the source, or pay them to recompile
it with a different maximum length.
> 2) I would like to have overloaded functions automatically resolved for command
> line execution to the non-object function as follows:
> When entering foo(0,1) at the serial command line, I want it automatically
> resolved to the function foo() and not foo_obj::foo(). The shell prompts for
> function resolution, but I don't want our users burdoned with that question
> since they will always be referring to foo() and not foo_obj::foo().
I would suggest that you make all symbols locals (or simply remove
them totally) once you have everything loaded. That will leave just
the ones you want in place.
That said, allowing unrestricted user access to the target shell is
something that I would recommend you do with extreme caution. There
are lots of things that they can call from the shell that will cause
odd problems. Since you have two problems with the shell, perhaps it
might be worth your while to create your own, simpler/safer one for
your end users?
Contribute to the VxWorks Cookbook at: