I am using jdll.h because I am trying to write verbs in C where the
bulk of the definition gets stored in a shared library.

It seems likely, now that I look closer, that jdll.h is the wrong
header for this purpose.  But that did not matter for my initial test
implementation of the shared library:

#include "system/examples/data/jdll.h"
void __stdcall __declspec(dllexport) example() {}

So far, my efforts have been a mix of google searches and simple tests.

I imagine that my shared library concepts will be more interesting
when I have progressed further (and I hope to eventually have portable
C, also).  Meanwhile, bugs, not completely relevant documentation and
incorrect assumptions are an integral part of the development process,
especially when breaking new ground.

-- 
Raul

On Wed, Jan 11, 2012 at 10:12 AM, Eric Iverson <[email protected]> wrote:
> I think everything should work in J7 except for cdf for the reasons Bill
> pointed out. In Windows post XP I think you could do your own call to the
> windows api to  unload your dll (making development testing easier). Not
> sure of the call name but it is something like freelibrary. I'm puzzled why
> this started out as a question about jdll.h which is about the J dll api
> and would seem to have little relevance to   building and using your own
> dll.
>
> On Wed, Jan 11, 2012 at 8:54 AM, Raul Miller <[email protected]> wrote:
>
>> I did not try jj.dll
>>
>> I was trying to write my own .dll
>>
>> I will live with j6, for now.
>>
>> Thanks,
>>
>> --
>> Raul
>>
>> On Tue, Jan 10, 2012 at 7:49 PM, Eric Iverson <[email protected]>
>> wrote:
>> > Raul,
>> >
>> > Bill is correct that cdf unload all dlls that cd has loaded. This wasn't
>> > too bad in the old J602 days, but is catastrophic in J7. In theory cdf
>> > could be made to take an argument to unload just a specific dll but, if I
>> > remember correctly, it doesn't because back in those early days unloading
>> > specific dlls caused all sorts of problems.
>> >
>> > Did you get the call to jj.dll to work? If so, you will have to live with
>> > that and not do the cdf.
>> >
>> > Please clarify for me if you got JDo to work or not.
>> >
>> > On Tue, Jan 10, 2012 at 7:35 PM, bill lam <[email protected]> wrote:
>> >
>> >> That example script said it only work for 32-bit windows, did you try
>> it in
>> >> 64-bits?  Some i should be changed to x in dll prototype in that case.
>> >>
>> >> Since gtkide has already opened a lot of gtk dlls, cdf will also free
>> >> those dlls and will crash.
>> >>
>> >> JHS opened libc or winsock dll for sockets.  I guess cdf will also crash
>> >> it.
>> >>
>> >> Втр, 10 Янв 2012, Eric Iverson писал(а):
>> >> > I have tried a few things and calling j.dll appears badly broken. I'll
>> >> look
>> >> > at this, but it may take a while for me to get to it.
>> >> >
>> >> > I'm puzzled by your reporting the problem as being with cdf. I get a
>> >> crash
>> >> > in JHS on the sentence:
>> >> >
>> >> >   'jj.dll JDo i *c' cd <cmd
>> >> >
>> >> > Does this work for you in jgtk? And then you get a crash doing the lib
>> >> free?
>> >> >
>> >> >
>> >> > On Tue, Jan 10, 2012 at 6:44 PM, Raul Miller <[email protected]>
>> >> wrote:
>> >> >
>> >> > > Ok, it's not the most urgent issue (though it's nice when #include
>> >> > > files like that can be relied on to be at a well known location).
>> >> > >
>> >> > > But here's another issue with that page:  when I use cdf'' in a j7
>> >> > > session, the ide crashes (I was using jgtk).  How are we supposed to
>> >> > > develop dll based apps in j7?
>> >> > >
>> >> > > --
>> >> > > Raul
>> >> > >
>> >> > > On Tue, Jan 10, 2012 at 2:25 PM, Eric Iverson <
>> >> [email protected]>
>> >> > > wrote:
>> >> > > > This file got left out from the 701 distribution.  There probably
>> >> should
>> >> > > be
>> >> > > > an addon for files like this but this probably isn't a high
>> >> priority. The
>> >> > > > file has not changed since 602.
>> >> > > >
>> >> > > > On Tue, Jan 10, 2012 at 1:52 PM, Raul Miller <
>> [email protected]>
>> >> > > wrote:
>> >> > > >
>> >> > > >> http://www.jsoftware.com/docs/help701/user/calling_jdll.htmsays:
>> >> > > >>
>> >> > > >>   "File system\examples\data\jdll.h. gives C prototypes for J
>> >> > > procedures."
>> >> > > >>
>> >> > > >> But this file does not exist under my j64-701 directory.
>> >> > > >>
>> >> > > >> --
>> >> > > >> Raul
>> >> > > >>
>> >> ----------------------------------------------------------------------
>> >> > > >> 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
>> >>
>> >> --
>> >> 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
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to