The linalg package works with the original array data structures in Maple V --- matrix, vector, and array, while the LinearAlgebra package works with the newer array data structures introduced in Maple 6 --- Matrix, Vector, and Array which support faster hardware floating-point operations.  In the code above it appears that you are trying to extract a column using the linalg package from a Matrix when you want to use the matrix data structure.  The key is that linalg was created before the Matrix, Vector, or Array data structures, and hence, you have to use matrix, vector, or array with linag.  Hope that this helps!  - David 

Hi Acer and Jakubi,

     Thanks to both of you for your interesting exchange.  I have been following your posts on this site for some time, and hence, I am glad to have a chance to hear from you on my question.  The problem with the classic interface is definitely GUI related --- i.e. it occurs when opening or closing a section, cutting and pasting a line or section, or moving the cursor too fast.  I have also encountered the problem that Maple 13 worksheets will freeze upon executing a command.  The problem occurs systematically in one Maple 13 file with Maple 16 but never with Maple 13.  This latter issue might be related to a change in rtables or an internal representation.  I do not know whether these problems were introduced in Maple 14, 15, or 16.  My guess would be 15 or 16 since the changes in 14 were relatively minor.  The types of GUI crashes are reminiscent of problems with Maple 6 that were corrected in Maple 8 and releases thereafter.  

      It would be good to have a simplified standard worksheet in the Java interface that resembles the classic version of Maple.  Then the Maple developers could combine the appeal of the classic worksheet's design with key extensions such as support for new plot structures and, most importantly, 64-bit architectures which are becoming the standard not just in Linux but also Windows.  R&D in revamping the standard Maple interface with a classic look taken into the future (perhaps with the addition of a Maple editor) is the best advance that Maple could presently make in their computer algebra system.  I have never enjoyed using the standard worksheet --- some new (or classic-inspired) direction is needed.

David

@ University of Chicago

Hi Acer and Jakubi,

     Thanks to both of you for your interesting exchange.  I have been following your posts on this site for some time, and hence, I am glad to have a chance to hear from you on my question.  The problem with the classic interface is definitely GUI related --- i.e. it occurs when opening or closing a section, cutting and pasting a line or section, or moving the cursor too fast.  I have also encountered the problem that Maple 13 worksheets will freeze upon executing a command.  The problem occurs systematically in one Maple 13 file with Maple 16 but never with Maple 13.  This latter issue might be related to a change in rtables or an internal representation.  I do not know whether these problems were introduced in Maple 14, 15, or 16.  My guess would be 15 or 16 since the changes in 14 were relatively minor.  The types of GUI crashes are reminiscent of problems with Maple 6 that were corrected in Maple 8 and releases thereafter.  

      It would be good to have a simplified standard worksheet in the Java interface that resembles the classic version of Maple.  Then the Maple developers could combine the appeal of the classic worksheet's design with key extensions such as support for new plot structures and, most importantly, 64-bit architectures which are becoming the standard not just in Linux but also Windows.  R&D in revamping the standard Maple interface with a classic look taken into the future (perhaps with the addition of a Maple editor) is the best advance that Maple could presently make in their computer algebra system.  I have never enjoyed using the standard worksheet --- some new (or classic-inspired) direction is needed.

David

@ University of Chicago