[DGD] Working with parse_string()

[Felix A. Croes]

Kamil N <kamiln at gmail.com> wrote:

>[...]
> By the way, is there any way I can somehow track runtime errors that
> happen inside parse_string() function, for example in LPC functions
> that are called by the parser? The most detailed error message I can
> get is:
>
> Runetime error: Index on bad type [caught]
>   46 receive_message   /kernel/obj/telnet (#25)
>  197 receive_message   /kernel/lib/connection (/kernel/obj/telnet#25)
>  232 receive_message   /usr/System/obj/user (#26)
>   37 input             /usr/System/obj/wiztool (#27)
>  763 call_limited      /kernel/lib/auto (/usr/System/obj/wiztool#27)
>  100 process           /usr/System/obj/wiztool (#27)
>  917 cmd_code          /kernel/lib/wiztool (/usr/System/obj/wiztool#27)
>   10 exec              /usr/admin/_code
>   39 do_parse          /usr/admin/parser_test
>
> Line 39 is just where I call parse_string() so it doesn't really help
> with finding in which LPC function this runtime error ocurred.

Line 39 is where the error is.  Had it been in a LPC function called
by parse_string(), the error trace would have included that function.

Regards,
Felix Croes