- rdnzl-devel@common-lisp.net - mailman3.common-lisp.net

[rdnzl-devel] My open source libraries (aka "ediware")
by Edi Weitz 31 Aug '11

31 Aug '11

[My apologies if you receive multiple copies of this email.] Hi everybody! As some of you will know, I'll start on a new job tomorrow. This new job won't involve much hacking, if at all, and thus it doesn't look like I'll have a lot of time to maintain my open source libraries in the near future. I have no plans to suddenly disappear from the CL world, but don't expect new releases of any of my libs any time soon. (At least none published by me or on my server.) Luckily, Hans Hübner - who already did most of the maintenance and development work for Hunchentoot in the last two years or so - offered to coordinate further development via github. See his full announcement at <http://netzhansa.blogspot.com/2011/08/ediware-moving-to-github.html>. I'll continue to read the mailing lists for my libs and I'm still interested in fixing bugs you might find in the release tarballs available on my web server. However, I will likely not bother to discuss or work on new features or compatibility code for implementations other than LispWorks (which happens to be the one I'm using). Lastly, I hope to see a lot of you in Amsterdam <http://weitz.de/eclm2011/> in October. The number of registrations so far has been pretty disappointing, but you still have three weeks left to change your mind... :) Take care, Edi.

1 0

[rdnzl-devel] Does rdnzl.tar.gz contain an up-to-date build of rdnzl.dll?
by Walter GR 06 Sep '10

06 Sep '10

Hi all, In brief: Attempting a minimal Windows Presentation Foundation application using the RDNZL 0.13.3 tarball and LispWorks Personal 5.1.1 resulted in a "The calling thread must be STA" error. Using a copy of rdnzl.dll built in Visual Studio C++ 2010 Express eliminated the error. Does rdnzl.tar.gz contain an old(er) build of rdnzl.dll, or is there something else at work? In detail: After appropriate calls to "import-assembly", "use-namespace", etc., I tried the following, and got the subsequent error: RDNZL-USER 9 > (let* ((win (new "Window")) (app (new "Application"))) (setf [%Height win] 300) (setf [%Width win] 300) [Run app win]) Error: .NET error (System.InvalidOperationException): The calling thread must be STA, because many UI components require this. 1 (abort) Return to level 0. 2 Return to top loop level 0. Type :b for backtrace, :c <option number> to proceed, or :? for other options I downloaded the current rdnzl-cpp tarball, and grepped for threading, finding RDNZL\RDNZL.vcxproj: <CLRThreadAttribute>STAThreadingAttribute</CLRThreadAttribute> RDNZL\Stdafx.cpp: System::Threading::Thread::CurrentThread->ApartmentState = System::Threading::ApartmentState::STA; Having no idea how to go about debugging the problem directly, I took a shot in the dark and built the DLL in Visual Studio C++ 2010 Express. It built fine. I replaced the existing rdnzl.dll and tried again: it worked perfectly! Let me know if I can provide any additional details. Thanks, Walter

2 1

[rdnzl-devel] Problem with 0.13.2 version?
by Rangarajan Krishnamoorthy 19 May '10

19 May '10

Hi, I am using LispWorks 6.0.1. I downloaded RDNZL 0.13.2 recently. When I do a (load "<path omitted>/load.lisp"), I get the following error message: The following function is undefined: RDNZL::CREATE-DIRECT-CALL which is referenced by RDNZL::REDEFINE-DIRECT-CALLS ; Loading fasl file G:\Downloads\Lisp\rdnzl-0.13.2\import.ofasl and after this my LW crashes. Any suggestions? Regards, Rangarajan

3 3

[rdnzl-devel] New release 0.13.3 (Was: Patch: bug fix for do-rdnzl-collection)
by Edi Weitz 18 May '10

18 May '10

Ugh, I finally managed to update RDNZL with your patch and released 0.13.3. Sorry for the long delay. Edi. On Mon, Mar 8, 2010 at 4:13 PM, Edi Weitz <edi(a)agharta.de> wrote: > Hi Raymond, > > Thanks for the patch. I'll be out of town for about a week and will > take care of this when I'm back. Please remind me if I don't... :) > > Edi. > > > On Mon, Mar 8, 2010 at 2:23 PM, Raymond Wiker <rwiker(a)gmail.com> wrote: >> The attached patch fixes a bug in do-rdnzl-collection. Without this >> patch, do-rdnzl-collection would stop processing after a collection >> member that evaluated to nil. >> >> _______________________________________________ >> rdnzl-devel mailing list >> rdnzl-devel(a)common-lisp.net >> http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-devel >> >> >

1 0

[rdnzl-devel] Make calls in the reverse direction (.NET -> CL)
by Joerthan Panest 24 Apr '10

24 Apr '10

My familiarity with .NET in this regard is fairly limited, but I was wondering what would be required to expose modules written in Common Lisp on top of .NET to other .NET modules. I'm afraid the answer might be some CLR Lisp implementation, of which there are few (if any) that are very mature that I know of. Basically, I have a fairly involved (LispWorks) Common Lisp module that was originally the entry point for a number of applications, which itself made calls to .NET components. The requirement has come up that I expose some of it's features to a .NET application and I'd like to avoid reimplementing all of it in C#. I'm not sure this is even an RDNZL question, but given that is my starting point I cannot help but wonder whether people have encountered the same issue given the nature of the problem RDNZL is solving.

4 10

[rdnzl-devel] Patch: bug fix for do-rdnzl-collection
by Raymond Wiker 08 Mar '10

08 Mar '10

The attached patch fixes a bug in do-rdnzl-collection. Without this patch, do-rdnzl-collection would stop processing after a collection member that evaluated to nil.

2 1

[rdnzl-devel] Fixed Assembly Resolver Example
by Seth Burleigh 14 Feb '10

14 Feb '10

When attempting to use the import assembly example from http://common-lisp.net/pipermail/rdnzl-devel/2008-February/000192.html I was having trouble. Basically, the fullname of the assembly was being passed in after I had officially loaded the assembly (it happens one time after attempting to create a new object in the assembly) and it was then trying to load something like AnAssembly, Culture=Neutral .dll So here i fixed it and you should do something like this to use it: (assembly-path! "C:/path/to/assembly/directory/" "/another/directory/") (install-assembly-resolver) I took the liberty of making install-assembly-resolver uninstall the previous assembly resolver if there were any. This is most likely the desired behavior since you dont want to install the same function each time.

1 0

[rdnzl-devel] rdnzl vs LWW6
by Paul Tarvydas 07 Feb '10

07 Feb '10

I wanted to have a look at rdnzl, but it crashes LWW6 when I load load.lisp (in init-rdnzl, probably inside the dll). Does anyone know how to fix this (or confirm that it works, hence, the problem is local to my machine)? thanks pt

2 4

[rdnzl-devel] Problems with Interop calls
by Eric 27 Dec '09

27 Dec '09

Hello everybody first off all i wanna thank you for this nice interface to the .Net-Framework. Now to my problem: I'm using RDNZL to control to ORC-Systems via .Net, my problem is that one OCR (tesseract) is working fine with it because it is possible to compile it with Microsoft Visual Studio(no problem at all). The other OCR-System ABBYY FineReader consits of DLL for which ABBYY provides an Interop-Assembly to communicate with it directly from the .Net-Framework. For controlling FineReader im using a C# Klasse (as an mediator in a DLL) which does futher action and intraktion with the OCR-System. If i use this Class direktly with a console-application compield in the .net-framework everything is fine. But if i use lisp and RDNZL to create an instance of the class and call a function of instance that calls _itself _a function of the ABBYY Interop-Assemble sometime the function call into the assembly don't came back. And if i start the process from Lispworks again everything works fine. Normally i would say it has nothing to do with RDNZL, but maybe it has some effects on the .Net-Framework which make it reacted different ??? So my question: Has someone experience with such a problem or does some know what i can do to find a workaround for this problem? -> When it stucks always the first call to the Interop-Assembly stucks, if this call don't stuck everything runs perfect. -> I also tried to call this Interop-Assembly directly with RDNZL with the same result, it sometimes stucks. Thanks a bunch for your help, Eric (If there is something unclear concerning my bad English and/or bad description i would be happy to describe it in detail) My System: - Win XP - LispWorks 5.1.1 Personal Edition - RDNZL 0.12.2. - Visual Studio 2008 Express Editions - .Net-Framework 3.5 Some Code: Unfortunately i can not provide an complete example or my full code, but here are at least some snippets. Also there happens nothing special, so i think the problem is somewhere else... and there is no exception coming back as if it is waiting or the call is not delivered. The function with starts the hole process in lisp: (defun OCR++FineReaderBildAuswerten (Speicherort bild sprache neuerSpeicherort ) (RDNZL:rdnzl-handler-case (let(dotNetList bilderAnzahl (ergebnis (list ) )) (OCR++FineReader-BilderPraeparieren (concatenate 'string Speicherort "\\" bild ) neuerSpeicherort) <<<---first Function to .Net see below (setq bilderAnzahl (- (OCR++FineReader-BilderAnzahl) 1)) (loop for n from 0 to bilderAnzahl do (OCR++FineReader-BilderOeffen n) (OCR++FineReader-InhaltAnalysieren ) (OCR++FineReader-InhaltAufbereiten sprache ) (OCR++FineReader-Speichern neuerSpeicherort bild :frz t :txt t) (setq dotNetList (OCR--FineReader-TextDatenStrukturLesen)) (setq ergebnis (cons (ORC--FineReader-erstelle-verschachtelterListe-Text dotNetList) ergebnis)) (OCR--FineReader-DokumentenAnalyseSaeubern)) (RDNZL:enable-rdnzl-syntax) (reverse ergebnis)) ( "System.Exception" (e) (print (RDNZL:invoke e "ToString") ) nil) )) =============================================== The first function which calls a function in the #Class: (defun OCR++FineReader-BildPraeparierenUndOeffnen(bild) (RDNZL:invoke fineref "bildPraeparierenUndOeffnen" bild ) ) =============================================== The function in the C# Class which calls a function of the Interop-Assembly: public Boolean bildPraeparierenUndOeffnen(String bildpfad) { Logger.logIT(this, " bildPraeparierenUndOeffnen: " + bildpfad, log); bildInformation = pEngine.PrepareAndOpenImage(bildpfad, bildBearbeitungsParameter, null, ref dokumentenInformation);*<<< here it stucks* Logger.logIT(this, " bildPraeparierenUndOeffnen: ende", log); return true; }

2 1

[rdnzl-devel] New release 0.13.2 (Was: New release 0.13.1)
by Edi Weitz 22 Dec '09

22 Dec '09

On Tue, Dec 22, 2009 at 12:14 PM, Raymond Wiker <rwiker(a)gmail.com> wrote: > Sooo, I think that maybe import-assembly should do something like > > (or [LoadWithPartialName ...] > (let (..) > [Load ...]) Yes, that's of course better. I should have thought of that myself... I made a new release with this change. Thanks and Happy Holidays, Edi.

1 0