[Coco] possible bug in the shell

[Wayne Campbell]

Thanks to Robert Gault I was able to figure out the problem,. It is not a
bug in the shell, it was me not assigning default values to certain
booleans before the error was generated that was the culprit.

Tip: make sure all variables in the error trap routine are DIM'd and
assigned default values before the error can be generated. That way you
always have those variables accounted for from the beginning of the
procedure.



On Mon, Apr 14, 2014 at 3:43 PM, Wayne Campbell <asa.rand at gmail.com> wrote:

> I don't know if any of Tormod's work applied to the shell at all, but in
> the 3.2.9 version I'm using, when I run decode with no parameter, instead
> of getting the output from the error trap (I'm trapping the 56 no parameter
> error), the cursor drops to the next line and sits there. I have to press
> [END] (equiv of [BREAK] on my keyboard) twice to break out. It must be a
> bug in the shell, because I never saw this behavior under the original OS-9
> L2 shell. Or with the original 1.2 shellplus I had back then. I was always
> able to trap for no parameter.
>
> Any possible fix for this? I really need to trap for the error.
>
> Wayne
>
> --
> The Structure of I-Code
> http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code
>
> decode
> http://cococoding.com/wayne/
>



-- 
The Structure of I-Code
http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code

decode
http://cococoding.com/wayne/