Edi Weitz edi-at-agharta.de |RDNZL-devel/via Sneakemail| wrote:
On Fri, 17 Feb 2006 21:14:02 -0500, "Dan Muller" s8ctxw402@sneakemail.com wrote:
But the other function that was giving me fits, Mesh.Cylinder, is blowing up for some other reason. At least it's getting called now -- progress!
Just to be sure: Are you using a version of LispWorks which can deal with foreign callbacks? This /could/ be the reason for strange things happening even if you yourself don't use a callback.
See recent discussions on this mailing list and here:
Thanks, but I don't think I'm running into this -- yet. I'll keep it in mind.
I was mistaken when I said that the float coercion is working. After struggling with Mesh.Cylinder to no avail, I wrote a very small test assembly in C#:
using System; using System.Collections.Generic; using System.Text; using System.Windows.Forms;
namespace ClassLibrary1 { public class Class1 { public Class1() { } public static void Yop() { MessageBox.Show("I am here! I am here!"); } public static void ShowSingle(Single f) { MessageBox.Show(f.ToString()); } public static void ShowDouble(Double f) { MessageBox.Show(f.ToString()); } } }
(I'm using VS 2005, thus .NET 2.0. Not that it should make much difference.)
Yop is used as a sanity check, and it works. I can successfully call ShowDouble with *c-d-f-t-s* nil. I can call both ShowDouble and ShowSingle with *c-d-f-t-s* t, but *both* show an incorrect result.
I haven't fetched the source for the RDNZL DLL yet, but I think that's my next step.
BTW, do you know any way (in Lispworks!) of forcing an assebmly to unload, so I don't have to restart the Lisp image whenever an assembly is changed?