September 2006 - rdnzl-devel@common-lisp.net

RE: [rdnzl-devel] Generic types and default thread apartment
by Goffioul Michael 15 Sep '06

15 Sep '06

> > Try this (tried with .NET 2): > > > > (rdnzl:enable-rdnzl-syntax) > > (rdnzl:import-types "System.Windows.Forms" "FolderBrowserDialog") > > (setq dlg (rdnzl:new "System.Windows.Forms.FolderBrowserDialog")) > > [ShowDialog dlg] > > > > This problem was the cause that made me recompile RDNZL-cpp under > > VS2005. If you look into StdAfx.cpp, you'll see how I changed the > > apartment state, but I don't know if it would work under > VC.NET-2003. > > So, do I understand correctly that you already experienced > these problems with the DLL compiled with VS2003? Yes. But this is not related to VS2003 itself. It just happened that I needed to modify the CPP code (to change the default apartment state) and that I only had VS2005 under the hand; hence I had to port the code to the new CLI/C++ interface. Michael.

1 0

[rdnzl-devel] Generic types and default thread apartment
by Goffioul Michael 14 Sep '06

14 Sep '06

Hi, I have 2 small questions: 1) does RDNZL support generic types? If yes, how do I create such an object using RDNZL syntax? 2) from a GUI perpective, it would be better to set the apartment state of the RDNZL.dll assembly to STA, otherwise various components do not work properly; is there a reason to not do it? Michael.

2 1

[rdnzl-devel] Handling of static events
by Goffioul Michael 14 Sep '06

14 Sep '06

Hi, I think that the RDNZL syntax does not handle static events correctly. Indeed, let's imagine I have a class ClassA that defines a static event EventB, then the following macro expansion is wrong: ECL-0.9i % (macroexpand '[+ClassA.EventB (rdnzl:new "System.EventHandler" #'identity)]) (RDNZL:INVOKE "add_ClassA" "EventB" (RDNZL:NEW "System.EventHandler" #'IDENTITY)) It should expand to (RDNZL:INVOKE "ClassA" "add_EventB" (RDNZL:NEW "System.EventHandler" #'IDENTITY)) Michael.

2 1

RE: [rdnzl-devel] Re: RDNZL and Mono
by Goffioul Michael 07 Sep '06

07 Sep '06

> > Do you think it is doable? Or is the package too Windows specific. > > The main point of the DLL which is delivered with RDNZL and > which is kind of a bridge between Lisp and .NET is the fact > that it mixes what Microsoft calls "managed" and "unmanaged" > code. Roughly, from the Lisp side it looks like plain old C > code, and from the .NET side it looks like, well, .NET code. > > AFAIU (but I'm not 100% sure), this can only be done with Microsoft's > C++, and not, e.g., with their C# or one of their other .NET > languages. There's surely /some/ way to do that with Mono > because Mono is open source and you'll be able to tweak it > somehow. However, I have no idea how to do that (and no time > to do it as well). Just wait a couple of months, I'm sure some GCC solution will popup :-) (apparently, there were some efforts in that direction in the context of Google SoC). Michael.

1 0

[rdnzl-devel] Re: RDNZL and Mono
by Edi Weitz 07 Sep '06

07 Sep '06

[Sending a copy to the mailing list. Maybe someone here has more to say about it.] On Thu, 7 Sep 2006 11:48:07 +0200, "Juan Jose Garcia-Ripoll" <juanjose.garciaripoll(a)googlemail.com> wrote: > Do you think it is doable? Or is the package too Windows specific. The main point of the DLL which is delivered with RDNZL and which is kind of a bridge between Lisp and .NET is the fact that it mixes what Microsoft calls "managed" and "unmanaged" code. Roughly, from the Lisp side it looks like plain old C code, and from the .NET side it looks like, well, .NET code. AFAIU (but I'm not 100% sure), this can only be done with Microsoft's C++, and not, e.g., with their C# or one of their other .NET languages. There's surely /some/ way to do that with Mono because Mono is open source and you'll be able to tweak it somehow. However, I have no idea how to do that (and no time to do it as well). I think that at least this shared library must be replaced. Everything in the Lisp code itself which might be Windows-specific shouldn't be too hard to port. Also, I don't know much about Mono, so I can't estimate how useful a Mono port would be. The good thing about RDNZL on Windows is that you have access to the whole operating system including all the GUI stuff. I guess this is not necessarily the case with Mono. HTH, Edi.

1 0

[rdnzl-devel] Re: New version 0.10.4
by Edi Weitz 05 Sep '06

05 Sep '06

Hi Michael! On Mon, 4 Sep 2006 12:26:03 +0200, "Goffioul Michael" <goffioul(a)imec.be> wrote: > BTW, another function improvement idea: I got to a situation where I > needed to import a type from an assembly whose DLL name didn't match > the namespace name, hence I couldn't use import-types. However, as > import-type requires an assembly object, I had to load it manually. > This is not a big deal, just annoying. Would it be possible to > provide a more flexible type importing function where you could > easily decouple the DLL and namespace names? (for instance by adding > an ":assembly" keyword to the import-types function) Yeah, I think that should be no big deal. I can do it, but not in the next days because I'm busy with other things. Feel free to submit a patch (preferably with updated documentation) in the meantime... :) Cheers, Edi.

1 0

[rdnzl-devel] FW: [Fwd: example apropos.lisp failed to load in ECL]
by Goffioul Michael 04 Sep '06

04 Sep '06

________________________________ From: Dean O'Connor [mailto:dean.oconnor@ite.com.au] Sent: Wednesday 30 August 2006 17:10 To: Goffioul Michael Subject: [Fwd: example apropos.lisp failed to load in ECL] hello michael I subscribe to the ECL mail list and was having a look at RDNZL. Pretty cool stuff. I just noticed an loading error for one of the examples. I tried to send the below info to the mail list but got rejected cause I wasn't subscribed - and don't really want to for just this one small thing. I assume you are, and was wondering if you'd mind posting this sometime. ps. I was very impressed by RDNZL. One of the few lisp packages I've downloaded and run (as per documentation) without hassle in ECL. cheers dean. -------- Original Message -------- Subject: example apropos.lisp failed to load in ECL Date: Thu, 31 Aug 2006 00:49:08 +1000 From: Dean O'Connor <dean.oconnor(a)ite.com.au> <mailto:dean.oconnor@ite.com.au> To: rdnzl-devel(a)common-lisp.net hello just trying out your RDNZL examples with ECL and noticed that apropos.lisp failed to load. RDNZL-USER> (load "examples/apropos.lisp") ;;; Loading "F:/projects/lisp/RDNZL-0.10.3/examples/apropos.lisp" (:CORMANLISP :ECL) is not a valid feature expression. Broken at LOAD. RDNZL-USER>> This change worked for me in ECL. In function copy-to-clipboard, I changed this line: #+(:cormanlisp :ecl) (setq apropos-text (lf-to-crlf apropos-text)) to this: #+(or :cormanlisp :ecl) (setq apropos-text (lf-to-crlf apropos-text)) Cheers deano

2 1