The best solution, if possible, would be to add a header to the page in
question that points to updated alternatives, or warning that it is related to
an outdated version of J.
On Saturday, November 27, 2021, 11:52:38 p.m. EST, 'robert therriault' via
General wrote:
Hi everyone,
A
It's been well over a decade since I last built a c# app which called
into J. (So treat the following with mild skepticism about the
accuracy of my memory.)
I don't remember marshalling data being a huge issue for what I was
doing. (Mostly, I was dealing with strings (which mostly were
executable
there is another page in jwiki.
guides / ole server for csharp
this page just contains enough information for interfacing to j ole server.
Users themselves must know more about csharp.
another way is the use of pinvoke to call j.dll from csharp. there is also
other pages on it but seems
IMO, the following are essential tutorials.
https://code.jsoftware.com/wiki/Studio/Building_Applications
https://code.jsoftware.com/wiki/Studio/Application_Distribution_-_Installer
https://code.jsoftware.com/wiki/Guides/J_CSharp
If they have up-to-date replacements, I do not find them.
I believe that these kinds of actions should include a "statement of
purpose". Is it because we think that these pages are irrelevant
and/or confusing and wish to emphasize different content?
At the moment, I am thinking particularly of
https://code.jsoftware.com/wiki/Stories/JohnHowland here.
