[ matlisp-Bugs-3513318 ] Wrong type declarations in src/quadpack.lisp

SourceForge.net <[email protected]> Sun, 22 Apr 2012 21:42:17 -0700
Newsgroups gmane.lisp.matlisp.devel
Message-ID <[email protected]>
Bugs item #3513318, was opened at 2012-03-30 10:42
Message generated for change (Comment added) made by rtoy
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513318&group_id=4511

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Ilya Perminov (iperminov1)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong type declarations in src/quadpack.lisp

Initial Comment:
Array IWORK is passed to functions that expect an array of F2CL-LIB:INTEGER4, but in initialization its element type is specified as (SIGNED-BYTE 32), 
In SBCL x64 F2CL-LIB:INTEGER4 and (SIGNED-BYTE 32) are different types.

Ilya


----------------------------------------------------------------------

>Comment By: Raymond Toy (rtoy)
Date: 2012-04-22 21:42

Message:
Thanks.  That's an oversight in the f2cl macros.l where no one bothered to
put in support for sbcl where integer4 should be (signed-byte 32).

However, with the upcoming ffi support, we can probably simply things and
get rid of the translated quadpack routines.  I'll have to think whether we
want to do that or not.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513318&group_id=4511

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2