Lispworks wasted no time going straight upside my head over an oddity caused by Freeglut history, I think: fonts are identified by enums 0, 1, 2 etc, but the parameter is declared in C as a pointer to a font! God bless static typing.
AllegroCL I guess does things helpfully in this regard if speed/safety are set right, if not it does things insanely/silently. Lispworks just slapped me. The upsetting thing is that a couple of hours ago I happened to notice that some calls to the glut font functions had the ID wrapped in (make-ff-pointer...) and others did not. I know I was tired at that point because one of my cardinal rules is to fix anything like that whether or not I think it is related.
Now Lispworks is yelling about something else. I do not think it should be, but I have to give LW the benefit of the doubt.
kt
Kenny Tilton wrote:
Lispworks wasted no time going straight upside my head over an oddity caused by Freeglut history, I think: fonts are identified by enums 0, 1, 2 etc, but the parameter is declared in C as a pointer to a font! God bless static typing.
AllegroCL I guess does things helpfully in this regard...
I forgot to mention: in some places I was just passing 0, 1, 2, 3 as integers, tho a pointer was required and specified in the FFI.
Now Lispworks is yelling about something else.
Unlikely to be the FFI, btw. Anyway, you all should definitely await the next distro if you get to the point where you are running the demos.
kt
-
Kenny Tilton