2009/11/15 Jeff Cunningham <j.k.cunningham(a)comcast.net>:
> In any event, now that I've seen Hans' request, I slapped my forehead for
> not seeing the debug statements, removed them, and here's the remade patch.
I've now uploaded release 0.5.7 which contains your patch.
Thanks,
Edi.
_______________________________________________
cl-gd-announce mailing list
cl-gd-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/cl-gd-announce
Thanks Raymond, I've just made a new release. I made a few cosmetic
changes, so please check if I didn't break anything.
On Tue, Nov 10, 2009 at 11:55 AM, Raymond Wiker <rwiker(a)gmail.com> wrote:
> I've had a little startup trouble with RDNZL, but this is mainly due to my
> lack of familiarity with .NET. The use of Load instead of
> LoadWithPartialName will most likely not be noticed by most people, but will
> provide (IMO) more helpful behaviour in case of errors. It can also be
> extended, at some later point, to use fully-qualified assembly names.
>
> The enclosed patch includes the trivial change to load-assembly, as well as
> a new macro called do-rdnzl-container. do-rdnzl-container does for general
> enumerable collections what do-rdnzl-arrays does for arrays.
>
> Thank you for making rdnzl available!
>
>
>
>
> On Nov 9, 2009, at 22:16 , Edi Weitz wrote:
>
>> Hi Raymond,
>>
>> I have to admit that I rarely, if ever, used RDNZL myself. I started
>> writing it for fun and only finished it because I gave a talk about
>> it. At that time I was ambitious enough to bring it into a usable
>> state, but as I didn't have any serious projects relying on it, I
>> didn't keep track with .NET development and I'm sure it's out of tune
>> now.
>>
>> If you have changes to make RDNZL better, I'm happy to accept patches,
>> but I won't be able to test or evaluate them due to lack of time.
>> I'll simply pack them into a new release if they follow the usual
>> patch guidelines:
>>
>> http://weitz.de/patches.html
>>
>> Thanks,
>> Edi.
>>
>>
>> On Mon, Nov 9, 2009 at 9:36 AM, Raymond Wiker <rwiker(a)gmail.com> wrote:
>>>
>>> Hi,
>>> I'm trying to use rdnzl to interface with certain .NET libraries.
>>> These libraries have a callback mechanism that requires me to subclass
>>> a C# class (or implement a C# interface) with two specific methods. I
>>> haven't seen any mention that RDNZL can be used to subclass C# classes
>>> (which I guess would be non-trivial to do), so I'm guessing that I
>>> need to write a C# wrapper class for interfacing with Lisp.
>>>
>>> I'm having certain problems with this, probably caused by some .NET
>>> details that I haven't (yet) understood. As part of unravelling this,
>>> I've discovered that import-assembly calls load-assembly and that a
>>> failure in load-assembly will cause a null assembly to be returned,
>>> from which import-assembly will import exactly zero items. In other
>>> words, any errors from load-assembly will not be signalled until
>>> later.
>>>
>>> The MS documentation states that LoadWithPartialName (as used by
>>> load-assembly) is an obsolete call, and that that
>>> System.Reflection.Assembly.Load() should be used instead. Load() can
>>> even be used with partial names, like this:
>>>
>>> (defun load-assembly-2 (name)
>>> (let ((fullname (new "System.Reflection.AssemblyName")))
>>> (setf [%Name fullname] name)
>>> [System.Reflection.Assembly.Load fullname]))
>>>
>>> I've just tried this, and load-assembly-2 gives an exception which is
>>> transferred perfectly through RDNZL in cases where load-assembly
>>> returns null.
>>>
>>> Regards,
>>> Raymond Wiker
>>>
>>> _______________________________________________
>>> rdnzl-devel mailing list
>>> rdnzl-devel(a)common-lisp.net
>>> http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-devel
>>>
>>>
>>
>> _______________________________________________
>> rdnzl-devel mailing list
>> rdnzl-devel(a)common-lisp.net
>> http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-devel
>
>
>
_______________________________________________
rdnzl-announce mailing list
rdnzl-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/rdnzl-announce
There's a new release 2.0.3 out which you can download from the usual
place. The change from 2.0.2 to 2.0.3 is only relevant to LispWorks
users.
Edi.
_______________________________________________
cl-ppcre-announce mailing list
cl-ppcre-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/cl-ppcre-announce
Hello,
A new version of Parenscript has been released. This release comes
with partial support for LOOP and DESTRUCTURING-BIND Common Lisp
facilities (thanks to the efforts of Daniel Gackle and Scott Bell),
much faster compilation speed, many bugfixes, real and efficient
lexical scoping for all special forms that introduce bindings, as well
as the ability to direct compiler output directly to a stream. One
thing that has been removed is support for the dot symbol notation (ie
- 'object.property' would be special cased into (slot-value object
'property) by the compiler) - this has been done to allow Parenscript
code to be a useful target for code walkers designed for regular Lisp
code. The consequence is that any code that relies on the dot notation
will need to be changed to use non-opaque object slot access.
Thank you,
Vladimir
_______________________________________________
parenscript-announce mailing list
parenscript-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-announce
A new release of CL-JSON packed with new features is now available,
thanks to Boris Smilga and Hans Hübner.
* Flexible CLOS decoder
* Greatly improved flexibility in customizing both the decoder and encoder.
* Various other improvements
* Backwards compatible
* Good supply of testcases
* Precise documentation (online)
http://common-lisp.net/project/cl-json
Big thanks to Boris!
Enjoy,
Henrik Hjelte
_______________________________________________
cl-json-announce mailing list
cl-json-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/cl-json-announce
Hi everyone,
I pushed a new version of cl-cairo2 to the GIT repository
http://github.com/tpapp/cl-cairo2/tree/master where it is kept now.
The most important change is that I disposed of the *context* global
variable, and moved context to the first argument, so now you write
(move-to context 0 -2)
instead of
(move-to 0 -2 context)
or
(setf *context*)
(move-to 0 -2)
I know this is an important change in syntax, and may break a lot of
code. I apologize for the inconvenience, but this has been a major
wart on the initial design and I have always wanted to fix it.
Best,
Tamas
_______________________________________________
cl-cairo2-announce mailing list
cl-cairo2-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/cl-cairo2-announce