For what it's worth:
I had this mostly written, but was bogging down. I would have needed
to implement transformation to 3!:2 format so that I could use JGetA
and JSetA (which would have been no big deal if I had been using them
all along -- all of my data is strings -- but not so good for a last
minute change).
Instead, I installed j602 (32 bit) on the user's machine and installed
sax and so on. Anyways, it turned out that my value error on
exec'Process.ijs' was because of a lack of write file permission and
using writefile which was defined on the line:
writefile_z_=: 1!:2 ::(1!:2 ([ wdstatus@('write file error: ',;))@])
when wdstatus itself was not defined... I should have had an
additional :: with a final 1!:2 for the case when the handler was
invalid.
So, anyways, the errors were my fault. But isolating my mistake was
hard (Process.ijs was 149 lines, and 54 of them contained '=:')
--
Raul
On Tue, Jun 28, 2011 at 1:23 PM, Raul Miller <[email protected]> wrote:
> Thank you.
>
> I had not considered making my code be the front end, though logically
> speaking that makes sense.
>
> This isn't anything I have done before, but I am studying up on
> PInvoke, and hopefully I'll be able to do something like this, soon.
>
> --
> Raul
>
> On Tue, Jun 28, 2011 at 9:58 AM, Eric Iverson <[email protected]>
> wrote:
>> 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
>>
>
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
