If try. temporarily turns off debugging, shouldn't that be documented? Thanks,
-- Raul On Wed, Jan 12, 2022 at 9:30 AM Henry Rich <[email protected]> wrote: > > The failing code isn't in a try. statement. It's in a different definition. > > try. turns off debugging unless you have a catchd. control word. Maybe > that would be called for here? > > Henry Rich > > > > On 1/12/2022 12:01 AM, Raul Miller wrote: > > When I run the attached (in a script) > > > > ex=: {{1+y}} > > exa=: {{try.ex y catch.end.}} > > 13!:0]1 > > 13!:3'ex 0' > > > > exa 4 > > 5 > > ex 3 > > |stop: ex > > | 1+y > > |ex[0] > > > > JVERSION > > Engine: j903/j64/darwin > > Release-a: commercial/2021-12-16T15:16:37 > > Library: 9.03.08 > > Qt IDE: 1.9.5/5.15.2(5.15.2) > > Platform: Darwin 64 > > Installer: J903 install > > InstallPath: /users/rauldmiller/applications/j903 > > Contact: www.jsoftware.com > > > > But I should be able to use the debugger on code wrapped in a try. > > statement. > > > > FYI, > > > > > -- > This email has been checked for viruses by AVG. > https://www.avg.com > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
