gmane.lisp.matlisp.devel

[ matlisp-Bugs-3604763 ] configure.ac assumes "."is in PATH

SourceForge.net — 2013-02-15T02:54:21

Bugs item #3604763, was opened at 2013-02-14 15:03
Message generated for change (Comment added) made by akssri
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3604763&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: compilation bugs
Group: None
Resolution: None
Priority: 1
Private: No
Submitted By: Ilya Perminov (iperminov1)
Assigned to: Akshay  Srinivasan (akssri)
Summary: configure.ac assumes "." is in PATH

Initial Comment:
There is a type in configure.ac line 380: "if a.out; then" should be "if ./a.out; then".



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

Date: 2013-02-14 18:54

Message:
Fixed.

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

Comment By: Akshay  Srinivasan (akssri)
Date: 2013-02-14 18:49

Message:
This should be a minor fix in configure.ac.

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

[ matlisp-Bugs-3604763 ] configure.ac assumes "."is in PATH

SourceForge.net — 2013-02-15T02:49:35

Bugs item #3604763, was opened at 2013-02-14 15:03
Message generated for change (Comment added) made by akssri
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3604763&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: compilation bugs
Group: None
Status: Open
Resolution: None
Private: No
Submitted By: Ilya Perminov (iperminov1)
Summary: configure.ac assumes "." is in PATH

Initial Comment:
There is a type in configure.ac line 380: "if a.out; then" should be "if ./a.out; then".



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

Date: 2013-02-14 18:49

Message:
This should be a minor fix in configure.ac.

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

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

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

[ matlisp-Bugs-3604763 ] configure.ac assumes "."is in PATH

SourceForge.net — 2013-02-14T23:03:36

Bugs item #3604763, was opened at 2013-02-14 15:03
Message generated for change (Tracker Item Submitted) made by iperminov1
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3604763&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: compilation bugs
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Ilya Perminov (iperminov1)
Assigned to: Nobody/Anonymous (nobody)
Summary: configure.ac assumes "." is in PATH

Initial Comment:
There is a type in configure.ac line 380: "if a.out; then" should be "if ./a.out; then".



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

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

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardw

Re: [Matlisp-commit] [matlisp-git]matlisp branchtensor updated. 2012-02-23-129-g2b87e86

Raymond Toy — 2012-07-13T15:43:20

On Fri, Jul 13, 2012 at 6:48 AM, Akshay Srinivasan <
akssri< at >users.sourceforge.net> wrote:


While I think I understand why you want to add this lower bound, it looks
like there will eventually be a global for each function.  That's just too
many.

Can't we just have one that is a rough tradeoff?  For people who need very
specific values, they can always rebind that one global for that one
function call.

Ray
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Matlisp-devel mailing list
Matlisp-devel< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlisp-devel

[ matlisp-Bugs-3527162 ] SVD gives an error: Thefunction (COMMON-LISP:SETF MATLISP:D

SourceForge.net — 2012-06-01T03:25:03

Bugs item #3527162, was opened at 2012-05-15 23:15
Message generated for change (Settings changed) made by akssri
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3527162&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
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Tzaddi (tzaddi)
Assigned to: Akshay  Srinivasan (akssri)
Summary: SVD gives an error: The function (COMMON-LISP:SETF MATLISP:D

Initial Comment:
It looks like setf (diag ...) is not defined properly or is not in the correct package.  When I run svd with job :a I get:

The function (COMMON-LISP:SETF MATLISP:DIAG) is undefined.

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

Comment By: Akshay  Srinivasan (akssri)
Date: 2012-05-29 11:12

Message:
Fixed in the matlisp-cffi branch.

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

[ matlisp-Bugs-3513323 ] SBCL does not likeconstant definition of +ffi-types+

SourceForge.net — 2012-05-29T18:13:27

Bugs item #3513323, was opened at 2012-03-30 10:59
Message generated for change (Settings changed) made by akssri
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513323&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)
Summary: SBCL does not like constant definition of +ffi-types+

Initial Comment:
SBCL signals "constant is being redefined " errors for +ffi-types+ and +ffi-styles+ in src/ffi-cffi.lisp, because the values of the constants are lists.
SBCL documentation explains the problem: http://www.sbcl.org/manual/Defining-Constants.html.

Ilya


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

Comment By: Akshay  Srinivasan (akssri)
Date: 2012-05-29 11:10

Message:
Yes, this happens to me on SB

[ matlisp-Bugs-3527162 ] SVD gives an error: Thefunction (COMMON-LISP:SETF MATLISP:D

SourceForge.net — 2012-05-29T18:12:46

Bugs item #3527162, was opened at 2012-05-15 23:15
Message generated for change (Comment added) made by akssri
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3527162&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
Priority: 5
Private: No
Submitted By: Tzaddi (tzaddi)
Summary: SVD gives an error: The function (COMMON-LISP:SETF MATLISP:D

Initial Comment:
It looks like setf (diag ...) is not defined properly or is not in the correct package.  When I run svd with job :a I get:

The function (COMMON-LISP:SETF MATLISP:DIAG) is undefined.

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

Date: 2012-05-29 11:12

Message:
Fixed in the matlisp-cffi branch.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2012-05-29 1

[ matlisp-Bugs-3513323 ] SBCL does not likeconstant definition of +ffi-types+

SourceForge.net — 2012-05-29T18:10:40

Bugs item #3513323, was opened at 2012-03-30 10:59
Message generated for change (Comment added) made by akssri
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513323&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: SBCL does not like constant definition of +ffi-types+

Initial Comment:
SBCL signals "constant is being redefined " errors for +ffi-types+ and +ffi-styles+ in src/ffi-cffi.lisp, because the values of the constants are lists.
SBCL documentation explains the problem: http://www.sbcl.org/manual/Defining-Constants.html.

Ilya


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

Comment By: Akshay  Srinivasan (akssri)
Date: 2012-05-29 11:10

Me

[ matlisp-Bugs-3527162 ] SVD gives an error: Thefunction (COMMON-LISP:SETF MATLISP:D

SourceForge.net — 2012-05-29T17:59:43

Bugs item #3527162, was opened at 2012-05-15 23:15
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3527162&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: Tzaddi (tzaddi)
Assigned to: Nobody/Anonymous (nobody)
Summary: SVD gives an error: The function (COMMON-LISP:SETF MATLISP:D

Initial Comment:
It looks like setf (diag ...) is not defined properly or is not in the correct package.  When I run svd with job :a I get:

The function (COMMON-LISP:SETF MATLISP:DIAG) is undefined.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2012-05-29 10:59

Message:
You should be doing:
 (copy! s (diag~ s1 0))

I'll add a setf-able me

[ matlisp-Bugs-3527162 ] SVD gives an error: Thefunction (COMMON-LISP:SETF MATLISP:D

SourceForge.net — 2012-05-16T06:28:35

Bugs item #3527162, was opened at 2012-05-15 23:15
Message generated for change (Comment added) made by tzaddi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3527162&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: Tzaddi (tzaddi)
Assigned to: Nobody/Anonymous (nobody)
Summary: SVD gives an error: The function (COMMON-LISP:SETF MATLISP:D

Initial Comment:
It looks like setf (diag ...) is not defined properly or is not in the correct package.  When I run svd with job :a I get:

The function (COMMON-LISP:SETF MATLISP:DIAG) is undefined.

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

Date: 2012-05-15 23:28

Message:
I found the definition in tensor.lisp, but am not sure why it can't be used
in svd.lisp.  So, I substituted

[ matlisp-Bugs-3527162 ] SVD gives an error: Thefunction (COMMON-LISP:SETF MATLISP:D

SourceForge.net — 2012-05-16T06:15:08

Bugs item #3527162, was opened at 2012-05-15 23:15
Message generated for change (Tracker Item Submitted) made by tzaddi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3527162&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: Tzaddi (tzaddi)
Assigned to: Nobody/Anonymous (nobody)
Summary: SVD gives an error: The function (COMMON-LISP:SETF MATLISP:D

Initial Comment:
It looks like setf (diag ...) is not defined properly or is not in the correct package.  When I run svd with job :a I get:

The function (COMMON-LISP:SETF MATLISP:DIAG) is undefined.

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

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

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

Merging matlisp-cffi to master branch?

Raymond Toy — 2012-04-28T16:13:06

Are we in a good enough state that we can merge the matlisp-cffi branch
to master?

Ray


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ matlisp-Bugs-3514241 ] config.lisp puts itssymbols into CL-USER

SourceForge.net — 2012-04-25T03:58:38

Bugs item #3514241, was opened at 2012-04-02 12:39
Message generated for change (Comment added) made by rtoy
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3514241&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
Priority: 5
Private: No
Submitted By: Ilya Perminov (iperminov1)
Assigned to: Nobody/Anonymous (nobody)
Summary: config.lisp puts its symbols into CL-USER

Initial Comment:
config.lisp puts its functions (MATLISP-VERSION and MATLISP-HERALD) into package CL-USER, but these functions are expected to be in 
MATLISP.


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

Date: 2012-04-24 20:58

Message:
Fixed.

Thanks.


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

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

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

SourceForge.net — 2012-04-25T03:18:46

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
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


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

Date: 2012-04-24 20:18

Message:
Fixed.  Use f2cl-lib:integer4 in quadpack.lisp and make f2cl-lib:integer4
be the same as (signed

[ matlisp-Bugs-3513323 ] SBCL does not likeconstant definition of +ffi-types+

SourceForge.net — 2012-04-23T04:43:16

Bugs item #3513323, was opened at 2012-03-30 10:59
Message generated for change (Comment added) made by rtoy
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513323&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: SBCL does not like constant definition of +ffi-types+

Initial Comment:
SBCL signals "constant is being redefined " errors for +ffi-types+ and +ffi-styles+ in src/ffi-cffi.lisp, because the values of the constants are lists.
SBCL documentation explains the problem: http://www.sbcl.org/manual/Defining-Constants.html.

Ilya


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

Date: 2012-04-22 21:43

Message:
Are you getting this because you ar

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

SourceForge.net — 2012-04-23T04:42:17

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


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

Date: 2012-04-22 21:42

Message:
Thanks.  That's an oversight in the f2cl macros.l where no one bot

[ matlisp-Bugs-3514241 ] config.lisp puts itssymbols into CL-USER

SourceForge.net — 2012-04-02T19:39:04

Bugs item #3514241, was opened at 2012-04-02 12:39
Message generated for change (Tracker Item Submitted) made by iperminov1
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3514241&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: config.lisp puts its symbols into CL-USER

Initial Comment:
config.lisp puts its functions (MATLISP-VERSION and MATLISP-HERALD) into package CL-USER, but these functions are expected to be in 
MATLISP.


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

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

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

[ matlisp-Bugs-3513323 ] SBCL does not likeconstant definition of +ffi-types+

SourceForge.net — 2012-03-30T17:59:22

Bugs item #3513323, was opened at 2012-03-30 10:59
Message generated for change (Tracker Item Submitted) made by iperminov1
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513323&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: SBCL does not like constant definition of +ffi-types+

Initial Comment:
SBCL signals "constant is being redefined " errors for +ffi-types+ and +ffi-styles+ in src/ffi-cffi.lisp, because the values of the constants are lists.
SBCL documentation explains the problem: http://www.sbcl.org/manual/Defining-Constants.html.

Ilya


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

You can respond by visiting: 
https://sourceforge.net

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

SourceForge.net — 2012-03-30T17:42:21

Bugs item #3513318, was opened at 2012-03-30 10:42
Message generated for change (Tracker Item Submitted) made by iperminov1
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


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1045

with-fortran-matrix

Raymond Toy — 2012-03-27T15:07:30

Now that I've used the callback support a little, I'd like to propose
the following to make it a little easier to write callbacks for fortran
routines.

(WITH-FORTRAN-MATRIX (name fv &rest dimensions) &body body)

This makes it easier to access Fortran matrices so you can write

(defun callback (fv)
  (with-fortran-matrix (m fv (1 4) (1 5))
    (setf (m 1 3) (m 4 5))

The dimensions (1 4) and (1 5) are the lower and upper bounds of the
Fortran matrix m, which is an alias to the actual foreign vector in fv.

Or maybe it should be

(with-fortran-matrices ((m1 fv1 <dims1>)
                        (m2 fv2 <dims2>))
  body)

so that several matrices can be created at once.

Ray

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

Re: Shadowing :cl functions

Raymond Toy — 2012-03-27T14:59:14

This has been done many times in several packages.  I did this for
maxima in the bigfloat package.  The intent was to be able to take
double-float code, through an (in-package "BIGFLOAT") around it, and
have it mostly work for Maxima's bigfloat.  I never measured it, but I'm
quite sure it is significantly slower than the original double-float
code.  There's the CLOS method lookup overhead and also lots of
additional boxing that probably needs to be done.
Perhaps.  But for me, I've concluded that it's not a good idea to just
use a package in another.  I prefer to keep the package prefix when
referring to other symbols from other packages.

Having said that, we should probably separate out the current matlisp
package into at least two packages.  There's the external matlisp
package that exports the exposed matlisp interface, and the internal
matlisp-internals package that has all the rest of the cruft for the
implementation.

Ray



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