It might be that what you are missing in your use of j.dll is the callback to get output. If you set a callback address for output then j.dll will call that routine for output such as the error information you are missing.
In j602 help highlights see section J Front End - Example Source Code as perhaps the simplest example of how to use the output callback. On Tue, Jun 28, 2011 at 7:02 AM, Raul Miller <[email protected]> wrote: > In other words, here? > > input=: 3 : 0 > term_append__locTerm prompt=: y > inputready=: 0 > inputs=: 0 > logged=: 0 > while. 1 do. > whilst. gtk_events_pending'' do. > gtk_main_iteration'' > end. > if. inputready do. break. end. > end. > if. ifxlog do. xlog=: xlog,<0;inputline end. > inputline > ) > > I am not seeing what you are seeing. > > I do see some plausible stuff in d.c in the gpl sources. But I do not > know how to use a gpl j.dll from .Net, so I have not been thinking > about working it from that angle. > > Perhaps I should? Regaining control in .net after a suspension seems > overly complicated. > > Anyways, if you have any suggestions I am all ears. > > (And this is too small of a project to hire isi for: If I asked for > funds, I would be told that I should not have used J in the first > place. I'm using J as a convenient way to parse some xml, and I have > been getting some errors when I run the code on the user's machine > which I do not get when I run it on my machine.) > > -- > Raul > > On Mon, Jun 27, 2011 at 8:01 PM, bill lam <[email protected]> wrote: >> In J frontends, errors were trapped by wdhandler or event handler >> and the frontend implements the necessary codes to get the name >> of verb where an error was raised. >> >> I imagine it would also be the responsbility of vb/c# interface >> itself to implement similar codes for error handling. >> >> -- >> regards, >> ==================================================== >> GPG key 1024D/4434BAB3 2008-08-24 >> gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
